I'm having a problem with an MVC (1.0) app that I can not understand at all. Two versions of the site hosted on the same server (Live and UAT) are for each version of the site, the same code is shared by multiple organizations, each with its own database (MSSQL2005) and IIS (7.5) A different web site (pointing to the same code).
The UAT site has an update of code and database that is waiting to be posted on the live site.
One of the customers ("Customer A") is getting an error "104: Reset Connection by Peer" When they try to log into UAT site they can see the login page, But when they submit their login details, the connection timed out (look like ~ 130 to complete the request).
Customers can log in to a Live site properly Other customers do not have problems signing in to UAT site or Live site. If I try to log in as Customer A, using their login details, it works well from within our network and outside of our network.
Customer A starts to use squid as a proxy. / P>
I can not think what the problem might be, and I have run away from the ideas of things for testing. The fact is that I can log in as a customer is fine and other customers have no problem because the code and database have to be eliminated as problems.
What can I do to try and separate the problem?
I was able to work something by removing the requested data (I'm guessing proxy ) Was withdrawing the prices of the form from the request. It clearly meant that the app was not working properly.
However, it appears that due to the removal of form data, the content-length was being unchanged, which tells why the client was ending waiting for more data and the server Thought it was finished.
Using https instead of HTTP (which we were going to do anyway), the request has to be stopped with tampering.
Comments
Post a Comment