Closed Bug 149630 Opened 22 years ago Closed 21 years ago

Getting "could not be found" on any page

Categories

(Core :: Networking: HTTP, defect)

Product:
Core
Component:
Networking: HTTP
Platform:
DEC
OpenVMS
Type:
defect
Priority:
Not set
Severity:
major

Tracking

()

Status:
VERIFIED INVALID

People

(Reporter: horn, Assigned: darin.moz)

References

(
URL
)

Details

Startup Mozilla, type in any address (ex. http://www.mozilla.org/ or 
http:/www.shsu.edu/) wether it is a local address (www.shsu.edu) or a remote 
address, get the following:

(Alert Window)
www.shsu.edu could not be found. Please check the name and try again.

                       (Ok button)

Running Build ID: 2002053008
Mozilla/5.0 (X11; U; OpenVMS Compaq_AlphaServer_ES40; en-US; rv:1.0.0) 
Gecko/20020530
Do you use a proxy ?

-> Networking:http
Assignee: Matti → darin
Component: Browser-General → Networking: HTTP
QA Contact: imajes-qa → tever
probably not a blocker since this is the only report of this problem...
Severity: blocker → major
We do have a proxy server. I changed the preferences to use the server and it 
did not seem to make a difference.
can you verify that the proxy server works as expected by doing a little test:

$ telnet proxyserver port
GET http://www.mozilla.org/ HTTP/1.0


after typing that line press enter twice and let us know what you see.  thx!
Starts off:

HTTP/1.0 200 OK
Server: Netscape-Enterprise/3.6
Date: Thu, 30 May 2002 09:56:55 GMT
Content-Type: text/html
ETag: "2bd14-34cb-3cf5dcff"
Last-Modified: Thu, 30 May 2002 08:04:15 GMT
Content-Length: 13515
Accept-Ranges: bytes
Age: 56
X-Cache: HIT from unxwc.shsu.edu
Proxy-Connection: close

then starts loading the www.mozilla.com page: 


<HTML>
<HEAD>

<TITLE>mozilla.org</TITLE>
<LINK REL="stylesheet" HREF="persistent-style.css" TYPE="text/css">
<LINK REL="icon" HREF="images/mozilla-16.png" TYPE="image/png">
</HEAD>
<BODY>

hmm.. that looks correct.  you might downgrading mozilla to HTTP/1.0 in the
Advanced->HTTP Networking prefs panel.  that may or may not be the problem...
hard to tell.
actually, did you specify your proxy server with its fully qualified domain name
(e.g.: proxy.mydomain.net) or did you just specify "proxy"?  i seem to recall
seeing a bug recently about mozilla failing to connect if you don't specify a
FQDN in the proxy prefs.  please confirm.
Concerning: actually, did you specify your proxy server with its fully 
qualified domain name
(e.g.: proxy.mydomain.net) or did you just specify "proxy"? I specified:
"Manual proxy configuration"
HTTP Proxy: unxwc.shsu.edu Port: 3128
No Proxy for: shsu.edu

This is the same way Netscape Version 4.79[en] - 20011017 on WinXP is 
configured.

On the message: you might downgrading mozilla to HTTP/1.0 in the
Advanced->HTTP Networking prefs panel.

Makes no difference.
what happens if you remove the "No Proxy For" setting?
Removing the "No Proxy for" setting makes not difference.
Can you post the output of the following:

$ set default sys$login
$ search [._mozilla...]prefs.js proxy,last_page

Proxies work on OpenVMS. This has to be a configuration issue of some sort.
James: can you please provide the information requested in comment 12 so that we
can try to diagnose this problem.
Also, is this a new problem which has just started happening? If so, what has
changed recently? Or are you a new Mozilla user and its never worked for you?
Results of "Comment 12":

user_pref
("browser.history.last_page_visited", "http://nell.shsu.edu/www/uafx03r.html");
user_pref("network.proxy.http", "unxwc.shsu.edu");
user_pref("network.proxy.http_port", 3128);
user_pref("network.proxy.type", 1);

=====
For "Comment 14": The previous versions of Mozilla were able to get to the 
sites. It stopped working one I installed the latest release.
This is very strange. So with previous versions of Mozilla you could access both
internal and extenal (to SHSU) pages without using a proxy server, right? And
now with Mozilla 1.0 you can't access internal or external sites at all, with or
without a proxy server defined? This doesn't make any sense.

What IP stack are you using? Don't tell me its Multinet or TCPware and you
forget to install their special version of LIBNSPR4!!!
I just talked to my contact at Process Software and he tells me that the
behaviour you are seeing is EXACTLY the symptom of not having the "Process
Special" LIBNSPR4 image.

http://www.process.com/techsupport/mozilla.html is the place to go. They haven't
gotten around to posting an image for 1.0 final yet (he says they'll do that
later today) but the 1.0-RC3 image should work just fine.

Please report back here if this is indeed the problem.
Ok, I don't remember if the previouse release was setup for the proxy server 
(I don't think it was), but I am using Multinet, and I do not think I used the 
special LIBNSPR4. 
I will get the special LIBNSPR4 on Monday and let you know what I find out.
Ok, after downloading the image LIBNSPR4, I am able to get to the sites (it is 
a lot slower).
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
Verified.
Status: RESOLVED → VERIFIED
REOPEN: was not fixed, should be WFM.
Status: VERIFIED → UNCONFIRMED
Resolution: FIXED → ---
RESOLVED/invalid.
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago → 21 years ago
QA Contact: tever → httpqa
Resolution: --- → INVALID
verified
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.