Problems with HTTP/1.1 and Netscape

Problems with HTTP/1.1 and Netscape

Post by Pierre Hali » Thu, 24 Feb 2000 04:00:00



Morning,

I recently move our Web site, previously hosted by a professionnal provider,
to our own Linux server running Apache 1.3 While everything is OK with IE
browser, it's impossible to read some pages using Netscape (every versions
included most recent). When I open a page I received only a text page with
source code.

If I look at the access_log file, I see

    for IE :                "GET / HTTP/1.1" 304 -
    for Netscape:    "GET / HTTP/1.0" 304 -

and I guess that Netscape receive a bad answer from the server

Thanks to help me

Pierre

 
 
 

Problems with HTTP/1.1 and Netscape

Post by Joshua Sliv » Thu, 24 Feb 2000 04:00:00



> Morning,
> I recently move our Web site, previously hosted by a professionnal provider,
> to our own Linux server running Apache 1.3 While everything is OK with IE
> browser, it's impossible to read some pages using Netscape (every versions
> included most recent). When I open a page I received only a text page with
> source code.
> If I look at the access_log file, I see
>     for IE :                "GET / HTTP/1.1" 304 -
>     for Netscape:    "GET / HTTP/1.0" 304 -
> and I guess that Netscape receive a bad answer from the server

Netscape doesn't use HTTP/1.1.  It uses 1.0 plus a bunch of extensions
that do some of the things that 1.1 does.  However, this is not your
problem.

Your problem is that you are not setting the mime type correctly on the
documents you are serving.  IE is ignoring the mime type and using the
file extension to decide how to display the file.  Netscape is following
your directions and displaying the file as text/plain.

Most likely, you have the problem described in
http://www.apache.org/docs/misc/FAQ.html#redhat-htm

--
Joshua Slive

http://finance.commerce.ubc.ca/~slive/

 
 
 

Problems with HTTP/1.1 and Netscape

Post by Nick K » Fri, 25 Feb 2000 04:00:00




Quote:>>     for IE :                "GET / HTTP/1.1" 304 -
>>     for Netscape:    "GET / HTTP/1.0" 304 -

>> and I guess that Netscape receive a bad answer from the server

304 means the document is unchanged and the server returned nothing.
Both browsers told the server they had a cached copy of your document,
and just wanted to verify it was up to date.

It probably has nothing to do with MSIE's failure to implement HTTP -
in this instance.

--
Nick Kew

We're so advanced here ... our nearest main road is called the A 386

 
 
 

1. apache http proxy - http/1.0 vs http/1.1

Hello,

I have setup an apache proxy, which seems to work fine. But, I found
out that it doesn't not answer back http/1.1 with a http/1.1 response.
The request comes in as 1.1, but the proxy answer back with 1.0. Is
there some special configuration I need to set in httpd.conf for it
to answer with a 1.1 response?

When I send traffic to the backend machine it will answer with a 1.1
response just fine. We are using the same version of apache for both
the proxy and actual backend server.

Any hints as to what I'm missing? Thanks.

-Dan

Sent via Deja.com http://www.deja.com/
Before you buy.

2. Help with fsck

3. Does Netscape for Linux use HTTP/1.1

4. KDE/Konqueror/Flash

5. http://home.netscape.com/eng/mozilla/1.1/handbook/docs/menus.html#C2

6. Digest authentication questions

7. Netscape Enterprise 3 HTTP 1.1 compliant?

8. ftp problem with Red Hat Linux

9. HTTP 1.0 or HTTP 1.1

10. http 1.0 or http 1.1

11. HTTP/1.0 vs HTTP/1.1 question

12. Apache Proxy question: HTTP/1.1 -> HTTP/1.0

13. HTTP 1.1 Header Problem.