Another (stupid) question about DA linking and proxy

[wierben]

Hi,

I see all links/commands in DA are hardcoded as /COMMAND which makes it impossible to proxy to a single "secure" domain, with subfolders for every DA server.. Is there a way arround this?

e.g. http://server.domain.tld:2222 proxy's to https://secure.domain.tld/server/

I don't want to buy a SSL certificate for every server :/ Or does one have a different suggestion to keep the http traffic secure?

Thanks

 

[zEitEr]

Hello,

Try and put your Proxy directives inside a <Location> section then.

Related:

http://httpd.apache.org/docs/2.2/mod/core.html#location
http://httpd.apache.org/docs/2.2/mod/mod_proxy.html

p.s. Did not test it myself yet.

 

[wierben]

I figured it out.

Ok, I fugured it out. You developers did not make it easy on us..

You have to enable the latest version of proxy_html (3.1.x - compile from source, debian(like) distro's ship 3.0.x, which doesn't work for DA).

Here's a config that works (good enough):

<VirtualHost *>
        ServerName secure.example.com

        ProxyRequests Off
        ProxyPreserveHost Off

        <Proxy *>
                Order deny,allow
                Allow from all
        </Proxy>

        ProxyPass /server01/ http://server01.example.com:2222/
        ProxyPassReverse /server01/ http://server01.example.com:2222/
        ProxyHTMLURLMap http://server01.example.com:2222 /server01

        <Location /server01/>
                ProxyPassReverse /
                ProxyHTMLEnable On
                ProxyHTMLExtended On
                ProxyHTMLURLMap / /server01/
                RequestHeader unset Accept-Encoding
        </Location>
</VirtualHost>

Mind the slashes, they have to be exactly as above..

Then in the proxy_html.conf (default config), add these lines (if using the default template, which I wont):

ProxyHTMLLinks  td              background
ProxyHTMLLinks  table          background

Because I won't be using the default template, I will not be looking for this error. DA developers were "kind" enough to insert HTML comments before and afer there javascript, beginning with a double slash, these slashes are replaced, making the javascript unrendered.. Which is not a big problem, since there just cosmetic.

Add some (access)log directives in your virtual host config, go ahead with SSL and you just cut enourmous costs in certificates..