On Fri, Sep 5, 2008 at 10:32 AM, Dragon <dragon@xxxxxxxxxxxxxxxxxx> wrote: > Dobes Vandermeer did speak thusly: >> >> > >> > OK, so then are you certain that the content type header is always being >> > sent? >> >> Yes, as far as I can tell it is always included in the HTTP dump that >> I get. Besides, which content-type includes the HTTP response headers >> in it? > > OK, after scanning through it pretty quickly, I have a suspicion what may be > happening. I suspect a blank line is getting > to the browser before the end of the headers and definitely before the > content type header. In such a case, the browser is likely to default to > plain text. Yeah, that seems possible. What I wonder about is that it happens so infrequently - I haven't seen it for a few days now. I'll keep an eye out for it and try and devise a way to reproduce it more reliably. I was hoping someone on the list had previously had this problem and found a solution. >> > Other than that, I am at a loss as to what might be happening. >> >> Me too :-( I wish I could reproduce this more frequently so that I >> could file a bug or something > > Well, we need a real good look at the HTTP transaction to determine that. Thanks for your help. --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx