Redirecting issues with ASP.NET and Safari

I am getting a very strange issue with the standard ASP.NET backend code and the latest Safari browser.

Basically, in the core ASP.NET code, we use normal response.redirect () calls, and sometimes in Safari, we just get a server down error, as if Safari can't connect to the server.

Unfortunately, this error is incompatible, so it is difficult to find a pattern.

Also, one of the developers reported that this happens even on regular anchors (i.e. no postback event, just a new request).

What can happen? Has anyone experienced this before?

I'm guessing this is either due to server redirects (but what could affect the browser?) ... or maybe some of our pages load strangely ... for example, maybe we are working with Page_OnLoad twice or something in sort of, and Safari thinks about it in a loop ...? but that not him ...

Any ideas?

UPDATE

We put the domain information on the site we were having problems with in our hosts file and the problem went away.

So it seems that safari is sometimes out of sync with DNS lookup.

Can anyone confirm this? and ... is there anything as a web developer I can do about it?

+2


source to share


2 answers


We put the domain information on the site we were having problems with in our hosts file and the problem went away.



So it seems that safari is sometimes out of sync with DNS lookup.

0


source


The best way to deal with such problems is to install a protocol analyzer like Ethereal or Wireshark and see what is being sent to the server. Compare traffic from Safari to that from IE. You can filter the output if you need to run the tool within a period to reproduce the problem.



+1


source







All Articles