Closed
Bug 135228
Opened 24 years ago
Closed 24 years ago
Blank pages, or no response to click on link
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
VERIFIED
WORKSFORME
People
(Reporter: william.kirkpatrick, Assigned: Matti)
References
()
Details
Attachments
(3 files)
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020313
BuildID: 2002031312
Using CUPS web interface. Pointing Mozilla at http://localhost:631 pulls up the
main page, but links are generally not responsive or, when they do anything,
they bring up a blank page.
Netscape 4.61 and MS-IE work fine.
Reproducible: Always
Steps to Reproduce:
1.Load CUPS with web interface.
2.Point Mozilla at http://localhost:631
3.Try and navigate.
Actual Results: Dead links, blank pages
Expected Results: followed links, shown pages.
Comment 1•24 years ago
|
||
Seen this. On test forms for our web application.
Cache problem.
If you clean the caches, problems disappears.
| Reporter | ||
Comment 2•24 years ago
|
||
Suggestion to clear the cache of no help. Main page works, looks like the urls
causing the problem is in the form 'http://localhost:631/jobs',
http://localhost:631/printers', etc. Is the lack of a file type extension
causing the problem?
| Assignee | ||
Comment 3•24 years ago
|
||
Reporter: Can you save the source from the main page and one link page and
attach it as compressed file ?
BTW: You can add a "normal" comment if you use the "Additional Comments" field
and hit the submit button.
Comment 4•24 years ago
|
||
just installed cups.
the pages work fine in both mozilla 0.9.9 and linux trunk 2002040302
| Reporter | ||
Comment 5•24 years ago
|
||
Request for html from linked page not possible. Mozilla either doesn't follow
the link, or when it does, "View - Page Source" gives an empty window.
| Reporter | ||
Comment 6•24 years ago
|
||
Requests, Responses, Headers, and Data for getting the CUPS main page and
trying for one of the non-working pages ('Current Printer Status'), under both
Mozilla and Netscape. CUPS seems, I think, to be spitting out bad HTML on the
non-working pages, (rendering data (<MAP>) in <HEAD> section). But, both NS
and IE work with it.
Comment 7•24 years ago
|
||
what version of CUPS are you running?
| Reporter | ||
Comment 8•24 years ago
|
||
Good question. I don't know how to ask CUPS the version question. When you
said "it works" I upgraded to current (1.1.14). Debian "stable" is installing
1.0.4-9, and my copy was somewhere in between.
So, about 1.1.14...
Much better, on a direct connection. Rarely, like twice in the last few hours,
I get a broken gif or blank page. Shift-"Reload" clears it up.
So, I pointed it at junkbuster (2.0.1) to see what changed. All went to hell.
Good pages, broken pages, broken gifs, errors from cups. All in seemingly
random combination. Use Shift-"Reload" and you're rewarded with a new and
wonderful variation each time.
In my world 'localhost' is excluded from the proxy, so I have a natural work
around. But something's funky, NS and IE have worked flawlessly across all
versions with, and without, junkbuster.
Comment 9•24 years ago
|
||
regarding junkbuster, you should make sure you have http version set to 1.0 in
Preferences -> Debug -> Networking.
junkbuster doesn't support http 1.1
| Assignee | ||
Comment 10•24 years ago
|
||
You can't see problems with junkbuster and :
NS use only http´/1.0
IE use Http/1.0 for proxys
and please clear the disk cache after you changed the Http Version to 1.0
Comment 11•24 years ago
|
||
what matti meant to say was that by default Netscape and IE use HTTP/1.0 for
proxies while mozilla uses 1.1
| Reporter | ||
Comment 12•24 years ago
|
||
Yes, I understand the 1.0 v. 1.1 thing. I agree with the choice to go with 1.1
as default -- it has to happen sometime. It's tough though, there are still 1.0
servers out there and the problem (their problem) isn't easily apparent to the
end-users.
Anyway, All seems well now. Maybe the cups problem was a 1.0 thing too.
I'd close this one as a documentation/stupid user problem. The only "fix" I
could think of would be to sense the server's first response and switch
accordingly. But that's a lot of work to accomodate what should be a rapidly
shrinking problem.
BTW, I picked up Mozilla a couple of days ago and it's already my default
browser. Fine job. Enigmail's ability to integrate so well package speaks
greatly about the overall design too. Thanks for the great package.
Comment 13•24 years ago
|
||
so upgrading cups made the problem go away?
| Reporter | ||
Comment 14•24 years ago
|
||
Yes, Cups is responding HTTP/1.0. But, even so, version 1.1.14 was working far,
far, better with Mozilla under 1.1 than whatever my older version was. Now that
I'm set to use 1.0 all is well.
So, upgrading cups helped greatly but, as I mentioned in comment 8, there was
the fairly rare odd event. Setting Mozilla to use HTTP 1.0 seems to have
cleared the problem completely.
| Assignee | ||
Comment 15•24 years ago
|
||
thanks for your answer
worksforme
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
Updated•21 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•