Matthias Vill wrote: > Hi there, > >>> We are returning 408 HTTP_REQUEST_TIMEOUT if anybody tries such a >>> request. Don't know if it's right thing to do? >>> Or we could also just close the connection. I don't know how browsers >>> react, since haven't found any "smart" ones. >>> >>> >> What happens on a 408, doesn't the user get an error page? >> > According to our best friend RFC 2616 for HTTP/1.1 > > 10.4.9 408 Request Timeout > > The client did not produce a request within the time that the server > was prepared to wait. The client MAY repeat the request without > modifications at any later time. > > So if the client has implemented 408 it is just perfect for our > situation as we don't get like "You 've been redirected"-messages or so > but can plainly tell the browser to retry. > Most propably there won't be any POST-requests, but many browsers do > complain on redirected POST-forms. > > Unfortunately , it didn't work. Internet explorer 6.0 got error and did not reload. Now testing with "connection close" method. This seems to be quite rare and not so straightforwardly reproduceable, since given same conditions I couldn't make it to the error page.
> Greetings > > Matthias > > ------------------------------------------------------------------------ > > _______________________________________________ > Peruser mailing list > [email protected] > http://www.telana.com/mailman/listinfo/peruser > _______________________________________________ Peruser mailing list [email protected] http://www.telana.com/mailman/listinfo/peruser
