httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sohum Misra <>
Subject Re: [users@httpd] Issues loading ASP.NET JavaScript on IIS7 through Apache mod_proxy
Date Wed, 02 Jun 2010 23:05:31 GMT

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/
    <Location />
        ProxyHTMLExtended On
        ProxyHTMLURLMap /myASPApp/ /

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 --> instead of just 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

Any thoughts?


The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:> for more info.
To unsubscribe, e-mail:
   "   from the digest:
For additional commands, e-mail:

View raw message