Re: Safari Timeouts, Status Codes 302, 200, and 400 Bad Request
- From: "JThomas" <jcthomas5@xxxxxxxxx>
- Date: 23 Jan 2006 18:43:05 -0800
Update:
The client says that after he had this trouble on his Mac Safari, he
tried Firefox 1.5 on a PC and also had the same problem. He's not
terribly descriptive of what happens on his end when the timeout
occurs, but the server log looked something like this:
GET /mypage1.aspx 200
POST /mypage1.aspx 302
GET /mypage2.aspx 200
POST /mypage2.aspx 200
--gave up, goes to another page on the site and exits--
Now... this looks a bit to me like he made it to page 2 just fine, and
then possibly submitted invalid data on page 2, or something, and just
didn't notice the red text that might have said 'please enter a valid
email address' or something.. and instead thought this was a timeout.
But he says it was a timeout, which I haven't been able to reproduce,
so I thought I'd mention it. Maybe a caching issue? ;o
Anyway, any ideas would be greatly appreciated.
Cheers,
John
.
- Follow-Ups:
- References:
- Prev by Date: Check Box !
- Next by Date: Using Indexing Service with dynamic TITLEs
- Previous by thread: Safari Timeouts, Status Codes 302, 200, and 400 Bad Request
- Next by thread: Re: Safari Timeouts, Status Codes 302, 200, and 400 Bad Request
- Index(es):
Relevant Pages
|
