This was discussed tome time ago. In principle you are correct but if tickets are not 200 OK IE does not display them.
Massimo On May 24, 2:17 am, Alexey Nezhdanov <[email protected]> wrote: > Here is my problem. > There is a javascript app that does asyncronous file upload. > It works nice with web2py when I test it on localhost, but when I > deliberately tried it over a slow link, I got this: > > Traceback (most recent call last): > File "/home/snake/python/horst/web2py/gluon/main.py", line 245, in wsgibase > int(request.env.content_length)) > File "/home/snake/python/horst/web2py/gluon/fileutils.py", line 268, in > copystream > data = src.read(chunk_size) > File "/home/snake/python/horst/web2py/gluon/wsgiserver.py", line 193, in > read > data = self.rfile.read(size) > File "/usr/lib/python2.5/socket.py", line 309, in read > data = self._sock.recv(recv_size) > timeout: timed out > > There is no any of my code in that trace so I can't affect how that is > processed. Yet, this trace returns a 200 HTTP page: (Internal error / Ticket > issued). javascript sees that return code is 200 and doesn't react properly > to the error. So here is the subject - since that's an internal error - > shouldn't it be HTTP(500) or at least HTTP(400) ? > > -- > Sincerely yours > Alexey Nezhdanov --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
