Re: Two issues - Brand new to ASProxy

Issue 1 happens because of some bugs in the "On the fly" javascript parser which asproxy relies on it.

To solve issue 2 you should have virtual directories. But you are hosting in IIS 7.5 and happened to have "Integrated mode" by default. You have two options to solve this, first is to change the "Integrated mode" to "Classic mode", second is to remove "httpModules" section from asproxy's web.config file.

And note that ASProxy is discontinued, so the bugs won't be fixed.

Regards.

On Friday, November 9, 2012 4:04:35 AM UTC+3:30, asproxyfan wrote:

Issue #1:  For some reason, I can't use the "Encode URLs" option if I go to facebook.com using ASProxy.  If I do, I can only see the top frame of the facebook webpage.  The rest of the webpage is an empty box.  If I disable this option, it facebook displays correctly; but, defeats the purpose of me trying to use asproxy (to obscurificate the URL).

Issue #2:  I need to use the below web.config in the root of my website (used for http to https redirect).  I have asproxy as a subdirectory with it's own web.config.  How can I make both web.config's work together (coexist).  Currently, when I try to use asproxy in a subdirectory, I lose the the webpage colors; and, getting a strange redirect error after trying to login to facebook.  This seems to be caused by the web.config I have in my root to forward http to https.  My web.config is definitely setup correctly for what it needs to do. I just dont know how to make both web.configs coexist.

I tried following the directions in the asproxy readme to use asproxy in a subdirectory; but, I dont think that's the problem since if I remove the web.config from the root, everything works fine.  However, I definitely need the web.config in the root of my website for it handle http to https.

---- web.config (root of my website)--------
<?xml version="1.0" encoding="UTF-8"?>
<configuration>
    <system.webServer>
        <rewrite>
            <rules>
                <rule name="HTTP to HTTPS redirect" stopProcessing="true">
                    <match url="(.*)" />
                    <conditions logicalGrouping="MatchAll">
                        <add input="{HTTPS}" pattern="off" ignoreCase="true" />
                        <add input="{REMOTE_ADDR}" pattern="127.0.0.1" negate="true" />
                    </conditions>
                    <action type="Redirect" redirectType="Found" url="https://{HTTP_HOST}/{R:1}" />
                </rule>
            </rules>
        </rewrite>
        <httpErrors errorMode="Custom" />
    </system.webServer>
</configuration>

I believe that there is no asp.net proxy available out. ASProxy is the only one.

On Saturday, November 10, 2012 6:18:10 AM UTC+3:30, asproxyfan wrote:

Thank you so much for replying.  So, what took ASProxy's place?  I'm hoping to find an opensource ASP.NET proxy that can handle some of the newer popular websites such as facebook; even when encoding URLs.