Eric,
Thanks for your response. I now have the mod_proxy_html module
installed in Apache2 and I can turn on the ProxyHTMLExtended option.
However, I'm still confused as to what I should be doing with the
mod_proxy_html module and where I should be putting it. I looked at a
couple of questions on this mailing list, and figured it should go
like this:
<VirtualHost *:80>
ProxyPass / http://localhost:8080/myASPApp/
ProxyPassReverse / http://localhost:8080/myASPApp/
ServerName myaspsite.mydomain.com
<Location />
ProxyHTMLExtended On
ProxyHTMLURLMap /myASPApp/ /
</Location>
</VirtualHost>
But the above doesn't work. When I look at the source for the page
that contains the JavaScript, it still has links as follows:
<link href="/myASPApp/WebResource.axd?..." type="text/css" rel="stylesheet" />
<script src="/myASPApp/WebResource.axd?..." type="text/javascript"></script>
<script src="/myASPApp/ScriptResource.axd?..." type="text/javascript"></script>
Strangely enough, the WebResource links somehow resolve through the
proxy (even though they are at a seemingly non-existent location -->
myaspsite.mydomain.com/myASPApp/WebResource.axd instead of just
myaspsite.mydomain.com/WebResource.axd). However, this was the case
even before I used the mod_proxy_html module. I thought the above
ProxyHTMLURLMap directive should have replaced all instances of
"/myASPApp/" with "/" to prevent the doubling of the local app path on
IIS7.
Any thoughts?
-Sohum.
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: [email protected]
" from the digest: [email protected]
For additional commands, e-mail: [email protected]
