714288 - cm.bell-labs.com - Code on http://cm.bell-labs.com/sys/doc/comp.html is incomprehensible

Status: RESOLVED INVALID

(Web Compatibility :: Site Reports, defect)

Description

[A, T]

Attachment: chromium and trunk comparison

http://cm.bell-labs.com/sys/doc/comp.html

Tested with Fx9 and tested with a new trunk profile, the issue persists, any code on the page is unreadable, Chromium works fine.

Here are several more confirmations
http://archive.installgentoo.net/g/thread/21929909#p21930478

Comment 1

[A, T]

Some new info. 
http://archive.installgentoo.net/g/thread/21929909#p21931047 

It was an character encoding issue, the site declares UTF-8 through xml, Nightly still continued with Western (ISO-8859-1) that led to the gibberish, even after reloading without cache several times and restarting, it still persisted, see:
 http://archive.installgentoo.net/g/thread/21929909#p21931260

Comment 2

[Tim (fmdeveloper)]

The site looks fine if I change the encoding it UTF-8...is the issue that Nightly didn't auto detect that fact?

Comment 3

[A, T]

Well, I don't really think you should change the encoding to read the site, since many people don't have UTF-8 as default. 

And also Nightly failed to switch the setting after changing it in the option screen, several times and after several restarts and ctrl+f5's, so there might be some cache issues here.

Comment 4

[Tim (fmdeveloper)]

(In reply to A, T from comment #3)
> 
> And also Nightly failed to switch the setting after changing it in the
> option screen, several times and after several restarts and ctrl+f5's, so
> there might be some cache issues here.

When I changed from Western to UTF-8 the page automatically refreshed and the UTF characters appeared correctly. Please test in Safe Mode and a new Profile.

Comment 5

[A, T]

>When I changed from Western to UTF-8 the page automatically refreshed and the UTF >characters appeared correctly. Please test in Safe Mode and a new Profile.

Safe mode didn't do a thing, it still showed the gibberish characters.
The new profile worked, though requiring a restart...

Comment 6

[Mats Palmgren (inactive)]

<?xml version="1.0" encoding="utf-8"?>

I think the above is ignored since the document is served as text/html

Adding charset info to the file or to the HTTP headers seems like the solution, eg:
<meta http-equiv="content-type" content="text/html; charset=UTF-8">

Comment 7

[Karl Dubost💡 :karlcow]

→ host cm.bell-labs.com
cm.bell-labs.com is an alias for plan9.bell-labs.com.
plan9.bell-labs.com has address 135.104.24.16
plan9.bell-labs.com mail is handled by 10 plan9.bell-labs.com.
plan9.bell-labs.com mail is handled by 90 aw.cs.bell-labs.com.


→ http HEAD http://cm.bell-labs.com/sys/doc/comp.html

http: error: ConnectionError: HTTPConnectionPool(host='cm.bell-labs.com', port=80): Max retries exceeded with url: /sys/doc/comp.html (Caused by <class 'socket.error'>: [Errno 51] Network is unreachable)


Let's close as INVALID