Getting "could not be found" on any page




Networking: HTTP
16 years ago
15 years ago


(Reporter: James T Horn, Assigned: Darin Fisher)



Firefox Tracking Flags

(Not tracked)





16 years ago
Startup Mozilla, type in any address (ex. or 
http:/ wether it is a local address ( or a remote 
address, get the following:

(Alert Window) 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) 
Do you use a proxy ?

-> Networking:http
Assignee: Matti → darin
Component: Browser-General → Networking: HTTP
QA Contact: imajes-qa → tever

Comment 2

16 years ago
probably not a blocker since this is the only report of this problem...
Severity: blocker → major

Comment 3

16 years ago
We do have a proxy server. I changed the preferences to use the server and it 
did not seem to make a difference.

Comment 4

16 years ago
can you verify that the proxy server works as expected by doing a little test:

$ telnet proxyserver port

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

Comment 5

16 years ago
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
Proxy-Connection: close

then starts loading the page: 


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

Comment 6

16 years ago
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.

Comment 7

16 years ago
actually, did you specify your proxy server with its fully qualified domain name
(e.g.: 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.

Comment 8

16 years ago
Concerning: actually, did you specify your proxy server with its fully 
qualified domain name
(e.g.: or did you just specify "proxy"? I specified:
"Manual proxy configuration"
HTTP Proxy: Port: 3128
No Proxy for:

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

Comment 9

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

Makes no difference.

Comment 10

16 years ago
what happens if you remove the "No Proxy For" setting?

Comment 11

16 years ago
Removing the "No Proxy for" setting makes not difference.

Comment 12

16 years ago
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.

Comment 13

16 years ago
James: can you please provide the information requested in comment 12 so that we
can try to diagnose this problem.

Comment 14

16 years ago
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?

Comment 15

16 years ago
Results of "Comment 12":

("browser.history.last_page_visited", "");
user_pref("network.proxy.http", "");
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.

Comment 16

16 years ago
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!!!

Comment 17

16 years ago
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. 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.

Comment 18

16 years ago
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.

Comment 19

16 years ago
Ok, after downloading the image LIBNSPR4, I am able to get to the sites (it is 
a lot slower).
Last Resolved: 16 years ago
Resolution: --- → FIXED

Comment 20

16 years ago

Comment 21

15 years ago
REOPEN: was not fixed, should be WFM.
Resolution: FIXED → ---

Comment 22

15 years ago
Last Resolved: 16 years ago15 years ago
QA Contact: tever → httpqa
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.