infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andy Seaborne (JIRA)" <>
Subject [jira] [Commented] (INFRA-4440) Migrate to ASF Infrastructure
Date Sun, 29 Apr 2012 14:31:48 GMT


Andy Seaborne commented on INFRA-4440:

Port 80 (for httpd).  (Port 22 for ssh :-)
Port 3030 only if that needs to be open for local redirection.  

If localhost:3030 works without opening it to the external network, that would be best but
either way works for us.

Our current setup is

<VirtualHost *:80>
  ProxyRequests off
  <Proxy *>
    Order deny,allow
    Allow from all
  ProxyPass / max=4
  ProxyPassReverse /
  ProxyPreserveHost On

Same for  port 3030 is not open 

However, there isn't some specific magic to that setup - anything that gets port 80 to port
3030 will do.  The rate limiting and the ability to add other httpd features like blocking
and caching if we ever need to is really why it is there; we haven't so far.  It also means
that admin of the service is user-space, but that isn't important.
> Migrate to ASF Infrastructure
> ----------------------------------------
>                 Key: INFRA-4440
>                 URL:
>             Project: Infrastructure
>          Issue Type: Wish
>      Security Level: public(Regular issues) 
>            Reporter: Lewis John McGibbney
> Currently we have a service demo running which displays use and functionality of the
Apache Jena.
> It would be great if we were able to migrate this demo to ASF infrastructure where it
now belongs.
> Some basic traffic statistics are provided below.
> -------------------
> is around 50 hits per hour (today).
> Quite a lot of syntax errors, which are cheap to process. Failure to count brackets,
failure to put <> around URIs, that sort of stuff.
> The demo server also implements query timeout - set to a few 10s of seconds currently
- and a limit on the amount of data it wil read from a remote location. 

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message