On Jun 11, 3:32 am, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > Hi Douglas, > > On Sun, 2007-06-10 at 21:32 -0700, DouglasPhillips wrote: > > I've got a really strange problem here. I've tried and tried to work > > it out, and have gotten nowhere. > > > I copied a customer's site as-is to a new server for development. > > Everything works as expected on the existing (production) server. > > > On the new development server, the site works as expected under IE, > > but under Firefox, I get a "The connection to (ip) was interrupted > > while the page was loading". Using various http sniffers, it appears > > that there is no proper status code being returned. > > In all cases? Or just to Firefox?
Opera is having the problem too. > The actual construction of the response happens in django/core/handlers. > You don't mention which serving environment you are using (development > server, but you can find where both modpython.py and wsgi.py are setting > the status_code for the return. You could check that the right values > are being set at that point, for a start. I'll look for that. The environment is using flup with Apache 2.0.27. > > Note that by the time the status code is set in the HTTP response in > those two modules, any response middleware has already been run. When > you say you are using the SSL Middleware, I guess you mean this > one:http://www.djangosnippets.org/snippets/85/? Never used it myself, but > from a quick read-through, there doesn't look to be anything wrong > there. Correct. > You might also need to look at pieces of your installation downstream > from Django. Are you using flup or something like that to hook up to the > webserver? Or mod_python? Is there anything else there that could be > working on the response before you see it on the network wire? > > I can't think of any way that Django would be sending out a reply > without the status code unless there is some really silly decorator or > middleware in the stack that is intentionally removing it. Grep for > status_code amongst all your third-party pieces to look for gremlins, > just in case. It does sound odd, though. I will try this. I'm also going to try doing a couple of other things to make sure this isn't some really strange apache problem. Thanks. -Doug --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
