Page do not open when Novell server needs login name and password




14 years ago
2 years ago


(Reporter: Pavol Svorc, Unassigned)


Windows 98

Firefox Tracking Flags

(Not tracked)


(Whiteboard: [DUPEME], URL)


(2 attachments)

164.88 KB, text/plain
279.94 KB, text/plain


14 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Win98; cs-CZ; rv:1.7) Gecko/20040616
Build Identifier: Mozilla/5.0 (Windows; U; Win98; cs-CZ; rv:1.7) Gecko/20040616

When I try use next URL, browser do not open the page where I may type login and
But if I use simle URL as I may type login and
password and then I can go to NWHealth page.
When I was logged, then I can use in new window too and it works OK. Only if I try it first
time I must use because doesn't work. 
In Internet Explorer when I use I may type
login and name and then browser go to /NWHealth automatically. 
The url is private Novell Netware server which has not
acces to public internet, but I think it doesn't matter.

Reproducible: Always
Steps to Reproduce:
1. You must use another URL that I described in 'details'
2. You must use URL as https://some.ip.address:some_port/Some_detail_page and
server need login name and password

Actual Results:  
The page can't display.

Expected Results:  
I think, page with login and name should be shown, then should be shown datail_page.

Comment 1

14 years ago
*** Bug 249954 has been marked as a duplicate of this bug. ***

Comment 2

14 years ago
can you create a http log : and attach the
log to this bug.

(When you've done trying to access the site: exit mozilla, to avoid collecting
too much irrelevant data in the log)
*** Bug 249954 has been marked as a duplicate of this bug. ***

Comment 4

14 years ago
Created attachment 152404 [details]
Log file

Here is the log file when I try open
Browser is waiting 'for server'... I must press cancel button.

Comment 5

14 years ago
Just to have tried it: 

Set the preference for Advanced->HTTP Networking to HTTP 1.0 for both direct
connection and proxy connection and see if that changes anything.
(Delete cache before trying again)
Also make sure you don't use pipelining - it's experimental.

Any change?

Comment 6

14 years ago
> Set the preference for Advanced->HTTP Networking to HTTP 1.0 for both direct

Yes, with  HTTP 1.0 it works OK. Is it problem in implementation HTTP 1.1 in

Comment 7

14 years ago
Some proxies aren't 1.1 compatible even if they claim to be.
Can you try setting only the proxy traffic to 1.0 and see what happens then
(Again: Delete cache before testing)
Assignee: general → darin
Component: Browser-General → Networking: HTTP
QA Contact: general → core.networking.http

Comment 8

14 years ago
Created attachment 152671 [details]

Here is next log. Proxy is set to http 1.0 and direct connect to 1.1. It
doesn't work again. It is maybe problem in mozilla. I don't use proxy at all.

Comment 9

14 years ago
Can you add your novell version and the name of the NLM for this service to the
summary to aid in searching. Thanks.
Also, try a newer version to see if that soves anything
Summary: Page do not open when server need login name and password → Page do not open when Novell server needs login name and password

Comment 10

14 years ago
This looks like a familiar problem.  Here's the interesting part of the log:

-16002981[78a010]: nsHttpTransaction::HandleContent [this=27f31e0 count=0]
-16002981[78a010]: nsHttpTransaction::HandleContentStart [this=27f31e0]
-16002981[78a010]: http response [
-16002981[78a010]:   HTTP/1.1 302 Object Moved Temporarily
-16002981[78a010]:   Server: NetWare HTTP Stack
-16002981[78a010]:   Date: Fri, 9 Jul 2004 09:26:28 GMT
-16002981[78a010]:   Location:
-16002981[78a010]:   Set-Cookie: loginReferralURL=/NWHealth; path=/
httpstkWMLlogin= ; path=/; expires=Friday, 01-Jan-1999 00:00:00 GMT
-16002981[78a010]:   Connection: Keep-Alive
-16002981[78a010]: ]
-16002981[78a010]: nsHttpConnection::OnHeadersAvailable [this=f814e0
trans=27f31e0 response-head=f86870]
-16002981[78a010]: Connection can be reused [this=f814e0 idle-timeout=300
-16002981[78a010]: waiting for the server to close the connection.

It would appear that the server never sends any message body along with the 302
like they are supposed to.  Moreover, it appears that the server never closes
the connection.  Based on the headers, we expect that the connection will stay
open until the server closes it.  Switching the client to HTTP/1.0 probably
works because it causes the server to generate a different response.  Can you
post a log file corresponding to the success case?  (i.e., when mozilla is
configured to speak only HTTP/1.0)  thx!

This does not look like a proxy server issue at all.

Looks like a server bug, but IIRC internet explorer manages to work around this
behavior by following the redirect straight away.  We should do the same.  I
think this is a duplicate bug report.  Confirming.
Ever confirmed: true
Whiteboard: [DUPEME]


14 years ago
Target Milestone: --- → mozilla1.8beta


13 years ago
Priority: -- → P2
Target Milestone: mozilla1.8beta1 → mozilla1.8beta2


13 years ago
Target Milestone: mozilla1.8beta2 → mozilla1.9alpha

Comment 11

12 years ago
-> default owner
Assignee: darin → nobody
Component: Networking: HTTP → Networking
QA Contact: networking.http → networking
Target Milestone: mozilla1.9alpha → ---
Is this still an issue ?
Last Resolved: 2 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.