Last post Feb 16, 2014 10:04 PM by Angie xu - MSFT
Feb 14, 2014 06:03 AM|cmal69|LINK
3 customers have the following problem.
When we access to the asp.net v4 web site (default.aspx), on
http://<servername> or http://localhost, we get a 504 http error (gateway timeout) instantly. With fiddler : error 301, wireshark : error 301, in the IIS logs : sc_status is 301.
The site has not moved, there is no redirection.
Accessing http://<website>/favicon.ico or http://<website>/foo.html works well.
We uninstalled and reinstalled IIS, executed aspnet_regiis with all options, on all .net versions. Problem still exists.
The IIS backup file contains correct references to ASP.Net 4 (isapi...).
The 3 customers are on Windows Server 2003 R2 SP2 (IIS 6).
One of them updated his server to Windows Server 2008 (IIS 7) : Problem still exists.
The 250 other customers don't have the problem.
we spent several days on this problem but no solution.
Someone already encountered this problem ? Someone has a solution ?
Feb 16, 2014 10:04 PM|Angie xu - MSFT|LINK
Thanks for your feedback.
Stop your existing application and ensure that you don't have any additional IIS process or instances of your local Web Server running, and check whether it helps you.
we get a 504 http error (gateway timeout) instantly.
The 504 Gateway Timeout error is an HTTP status code that means that one server did not receive a timely response from another server that it was accessing while attempting to load the web page or fill another request by the browser.
You could check the flow of IP data traffic between various computers and find out at which server,traffic is blocked.