> I've fixed this as of http://code.djangoproject.com/changeset/3530 .
> Thanks for bringing it up!
Works like a charm. thanks. Such a tiny piece of code... :)
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Djang
On 7/31/06, Akatemik <[EMAIL PROTECTED]> wrote:
> I'm running the basic django server and everything works fine from lan.
> But from outside every request has a three second overhead, even if
> it's just a 304. This means that a small html-page with three JS-files
> and a stylesheet takes 15 secon
Malcolm Tredinnick wrote:
> Um, Dave? The original poster was using the development server. Apache
> doesn't get a seat at the table here. :-)
Er ... in my best Emily Litella impression: "Never mind"
--~--~-~--~~~---~--~~
You received this message because you ar
On Wed, 2006-08-02 at 14:01 +, DavidA wrote:
>
> Akatemik wrote:
> > > In my experience, when you encounter non-obvious but fairly consistant
> > > slow
> > > downs in net traffic, the first thing to check is DNS.
> > >
> > > In this case, I'd make sure that each of the DNS cache servers tha
Akatemik wrote:
> > In my experience, when you encounter non-obvious but fairly consistant slow
> > downs in net traffic, the first thing to check is DNS.
> >
> > In this case, I'd make sure that each of the DNS cache servers that the
> > client
> > consults to resolve the address of your server
> In my experience, when you encounter non-obvious but fairly consistant slow
> downs in net traffic, the first thing to check is DNS.
>
> In this case, I'd make sure that each of the DNS cache servers that the client
> consults to resolve the address of your server can perform both a forward and
On Monday 31 July 2006 22:04, Akatemik wrote:
> I'm running the basic django server and everything works fine from lan.
> But from outside every request has a three second overhead, even if
> it's just a 304. This means that a small html-page with three JS-files
> and a stylesheet takes 15 sec
On 7/31/06, Akatemik <[EMAIL PROTECTED]> wrote:
> I'm running the basic django server and everything works fine from lan.
> But from outside every request has a three second overhead, even if
> it's just a 304. This means that a small html-page with three JS-files
> and a stylesheet takes 15 secon
I wasn't running Apache with Django, just confirming that there isn't a
connection problem with my normal pages.
Hmm, I'll look into the source and see if I can make the server print
something. If it doesn't work, I guess I just have to set Apache up.
Wouldn't think that as necessary though, sinc
On Mon, 2006-07-31 at 03:04 -0700, Akatemik wrote:
> I'm running the basic django server and everything works fine from lan.
> But from outside every request has a three second overhead, even if
> it's just a 304. This means that a small html-page with three JS-files
> and a stylesheet takes 15 se
I'm running the basic django server and everything works fine from lan.
But from outside every request has a three second overhead, even if
it's just a 304. This means that a small html-page with three JS-files
and a stylesheet takes 15 seconds to load.
With apache everything works fine even from
11 matches
Mail list logo
