www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin Grigorov (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (INFRA-10222) ProxyPass for Wicket static site sub-directory
Date Sun, 18 Oct 2015 09:18:05 GMT

     [ https://issues.apache.org/jira/browse/INFRA-10222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Martin Grigorov updated INFRA-10222:
    Priority: Blocker  (was: Minor)

> ProxyPass for Wicket static site sub-directory
> ----------------------------------------------
>                 Key: INFRA-10222
>                 URL: https://issues.apache.org/jira/browse/INFRA-10222
>             Project: Infrastructure
>          Issue Type: Wish
>      Security Level: public(Regular issues) 
>            Reporter: Martin Grigorov
>            Priority: Blocker
> I would like to ask whether it is possible to enable ProxyPass HTTP directives for a
sub-directory of Apache Wicket static site.
> At the moment http://wicket.apache.org/ is completely static, i.e. it consists only of
.html, .css and .js files.
> We would like to add reverse proxy directives so that http://wicket.apache.org/examples/7.x
proxies an external Apache Tomcat installation that will serve our examples.
> I've played locally with the setup and what is needed to be added to apache2.conf is
something like:
> {code}
> ProxyRequests off
> ProxyPass         /examples/7.x/ http://examples7-apachewicket.rhcloud.com/
> <Location /examples/7.x/>
>     ProxyPassReverse  /
> </Location>
> {code}
> I'd not bother Infra team and just use .htaccess but unfortunately Proxy directives are
not allowed in .htaccess file.
> So my question is: is it OK to have this proxy setup for our site?
> If YES, then please add a second entry for our 6.x releases:
> {code}
> ProxyRequests off
> ProxyPass         /examples/6.x/ http://examples6-apachewicket.rhcloud.com/
> <Location /examples/6.x/>
>     ProxyPassReverse  /
> </Location>
> {code}

This message was sent by Atlassian JIRA

View raw message