Closed
Bug 177060
Opened 23 years ago
Closed 22 years ago
Gopher type 0 (text file) pages not displayed
Categories
(Core :: Networking, defect)
Tracking
()
VERIFIED
DUPLICATE
of bug 202188
People
(Reporter: seanm, Assigned: bbaetz)
References
()
Details
(Keywords: regression)
I upgraded from the 0.1 to 0.3 version of Phoenix. (Note: I am not allowed to
fill in the version part of the bug report) Directories seem to work, but I can
no longer access text or binary files. I know this worked in 0.1 and I *believe*
I have 0.2 at work and it works.
Thanks,
Sean MacLennan
Comment 1•23 years ago
|
||
gopher://seanm.ca/ WFM on a 10/26 build.
sean, I don't know a lot about the gopher protocol or servers, but are you sure
it's not a config problem?
Comment 2•23 years ago
|
||
ok I see this now, I wasn't checking txt docs.
Status: UNCONFIRMED → NEW
Component: General → Networking
Ever confirmed: true
Product: Phoenix → Browser
Version: unspecified → other
![]() |
||
Comment 3•23 years ago
|
||
reassign for real. This is a problem in Mozilla too.
Assignee: blaker → new-network-bugs
QA Contact: asa → benc
Comment 4•23 years ago
|
||
regression between linux trunk builds 2002092221 and 2002092408
Keywords: regression
Comment 5•23 years ago
|
||
Bradley, are you still fixing gopher problems?
Assignee: new-network-bugs → dougt
Comment 6•23 years ago
|
||
.
Assignee | ||
Comment 8•23 years ago
|
||
I'm not touching anything for the next cuople of weeks at least...
Reporter | ||
Comment 9•23 years ago
|
||
I couldn't wait a couple of weeks ;-) So I looked into it. I noticed that html
files seemed to view fine, directories where fine, but text files just did nothing.
In the function nsGopherChannel::GetContentType I changed the type for text
('0') from TEXT_HTML to TEST_PLAIN and now I can view text files. This is
probably the correct setting anyway.
I see from the readme you do not accept patches, but since it is only one word I
thought I would include it to try to expedite the fix.
Index: netwerk/protocol/gopher/src/nsGopherChannel.cpp
===================================================================
RCS file: /cvsroot/mozilla/netwerk/protocol/gopher/src/nsGopherChannel.cpp,v
retrieving revision 1.27
diff -u -r1.27 nsGopherChannel.cpp
--- netwerk/protocol/gopher/src/nsGopherChannel.cpp 16 Sep 2002 19:46:27
-0000 1.27
+++ netwerk/protocol/gopher/src/nsGopherChannel.cpp 30 Oct 2002 05:46:40 -0000
@@ -331,7 +331,7 @@
switch(mType) {
case '0':
- aContentType = NS_LITERAL_CSTRING(TEXT_HTML);
+ aContentType = NS_LITERAL_CSTRING(TEXT_PLAIN);
break;
case '1':
switch (mListFormat) {
Assignee | ||
Comment 10•23 years ago
|
||
I happily accept patches :)
We should be running this through the text->html converter - did that get lost
somewhere with those other content type changes which went in a few weeks back?
darin? dougt? any ideas?
Without this patch, does view-source show the correct text?
Comment 11•23 years ago
|
||
*** Bug 149322 has been marked as a duplicate of this bug. ***
Comment 12•23 years ago
|
||
*** Bug 164283 has been marked as a duplicate of this bug. ***
Reporter | ||
Comment 13•23 years ago
|
||
> We should be running this through the text->html converter - did that get lost
> somewhere with those other content type changes which went in a few weeks back?
I updated from cvs to the latest code (0.5). The text->html converter *is* the
problem. If you comment out the special case for '0' in
nsGopherChannel::OnStopRequest then you can see the text files. (You also still
want the TEXT_HTML to TEXT_PLAIN patch to make the files readable).
Comment 14•23 years ago
|
||
If this is text-only, can we someone update the summary to be more specific?
Reporter | ||
Updated•23 years ago
|
Summary: Gopher pages not working → Gopher type 0 (text file) pages not displayed
Comment 15•23 years ago
|
||
*** Bug 190132 has been marked as a duplicate of this bug. ***
Assignee | ||
Comment 16•22 years ago
|
||
This got fixed.
*** This bug has been marked as a duplicate of 202188 ***
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•