http is not registered protocol
Max
The latest build (01/31) constantly reports "http is not registered protocol", and cannot access any sites.
Max
Mikus Grinbergs
>
> The latest build (01/31) constantly reports "http is not registered protocol", and cannot access any sites.
I'm running 2003013109. It works fine for me.
mikus (I don't use Mozilla for mail, chat, etc.)
Leo Tick
of course it works fine for you you are not using the services which fail.
For me the current nightly is better but not good
Mikus Grinbergs
When I look at some Russian sites, I don't see where in View ->
Page Source there is much difference in the <head> content between
the Russian-language page and the English-language page, yet
View -> Page Info -> Encoding correctly indicates that respective
Russian and Western character sets are being used to show the two
different pages versions. [In other words, with these sites I can
trust what View -> Page Info -> Encoding reports.]
But http://www.karl-h-wittenburg.de/nsqs/index.html seems to have
its "encoding" decided upon by MOZILLA, not by the server !!
When my Preferences -> Navigator -> Languages -> Default Character
Coding specifies 'UTF-8', View -> Page Info -> Encoding claims
this page is encoded in 'UTF-8', and mozilla shows the accented
characters on this page as black diamonds enclosing a question mark.
When my Preferences -> Navigator -> Languages -> Default Character
Coding specifies 'Western ISO-8859-1', View -> Page Info ->
Encoding claims this page is encoded in 'ISO-8859-1', and mozilla
shows the correct accented glyphs for those same characters.
The German case makes me think that View -> Page Info is
"untrustworthy". Rather than telling me what the SERVER said
about the page (e.g., "Encoding Not Indicated"), mozilla appears
to be substituting its own value without telling me it had done so.
mikus (2003013109)
Wolfi
But at least this build finally loads again on my system.
Wolfi
--
K6-2+/450, Warp4 FP15, Krnl14.093c, Mozilla 1.3b Build 20030115 + Multizilla 1.1.3.3B
Fight TCPA before it's to late! <www.notcpa.org/members.html>, <www.againsttcpa.com>
NO Digital Restrictions Management (DRM)
Paul Gorodyansky
> I'm not comfortable with View -> Page Info -> Encoding
>
> When I look at some Russian sites, I don't see where in View ->
> Page Source there is much difference in the <head> content between
> the Russian-language page and the English-language page, yet
> View -> Page Info -> Encoding correctly indicates that respective
> Russian and Western character sets are being used to show the two
> different pages versions. [In other words, with these sites I can
> trust what View -> Page Info -> Encoding reports.]
Right. It's because these sites follow the W3C guidelines:
setting the encoding vi HTTP Header (which is sent by the
Web Server alomg with page itself) is more preferrable than
hard-coding the encoding name in the HTML text itself via
<meta http-equiv="Content-Type" content="text/html; charset=...">
in the <HEAD> section.
What you see in View/PageInfo _is_ HTTP Header.
>
>
> But http://www.karl-h-wittenburg.de/nsqs/index.html seems to have
> its "encoding" decided upon by MOZILLA, not by the server !!
>
> When my Preferences -> Navigator -> Languages -> Default Character
> Coding specifies 'UTF-8', View -> Page Info -> Encoding claims
> this page is encoded in 'UTF-8', and mozilla shows the accented
> characters on this page as black diamonds enclosing a question mark.
>
> When my Preferences -> Navigator -> Languages -> Default Character
> Coding specifies 'Western ISO-8859-1', View -> Page Info ->
> Encoding claims this page is encoded in 'ISO-8859-1', and mozilla
> shows the correct accented glyphs for those same characters.
>
>
> The German case makes me think that View -> Page Info is
> "untrustworthy". Rather than telling me what the SERVER said
> about the page (e.g., "Encoding Not Indicated"), mozilla appears
> to be substituting its own value without telling me it had done so.
>
> mikus (2003013109)
Interesting... I am at home and will be able to check Mozilla
only tomorrow, but my Netscape 4.8 (Windows 2000)
works OK - my Default encoding is Cyrillic(Windows-1251) and when
I go to that German site and do View/Page Info, it correctly tells
me
"Charset: Unknown".
Could you post your findings into the Internationalization
Newsgroup and/or fiel a bug into BugZilla?
The Newsgroup is netscape.public.mozilla.i18n
--
Regards,
Paul Gorodyansky
"Cyrillic (Russian): instructions for Windows and Internet":
http://ourworld.compuserve.com/homepages/PaulGor/
Max
> I also get this with 20030131. Mail/News isn't loading any postings either.
> But at least this build finally loads again on my system.
I believe, the crash bug was transformed into this one.
Does "ping 127.0.0.1" work on your system? I guess, it doesn't ;-)
Max
Wolfi
I cannot test any more the buggy builds, since I already removed and deleted all
versions later than the one I'm currently using and previously downloaded over my
slow modem dial-up connection :-(
It was only a waste of precious disk space.
Wolfi
--
life...@xxvol.com
>I also get this with 20030131. Mail/News isn't loading any postings
>either. But at least this build finally loads again on my system.
I'm getting it on 20030202 - immediately upon startup (homepage) and any
time I try to connect to any specific site. And, whatever it has to do
with it, I do get a good ping on 127.0.0.1.
Jim L
Snip XX to Email
Heck with spies in Iraq. Bush should tell all the secrets he knows!!
Paul Gorodyansky
I have just checked MOzilla 1.3a on Windows 2000 - yes, you
are right, there is such problem (error), so it's not just on OS2...
Max
Wolfi
Wolfi
Max wrote:
>
> http://bugzilla.mozilla.org/show_bug.cgi?id=191739
Michael Kaply
> Is Darin's fix already in today's 12h build?
>
> Wolfi
>
> Max wrote:
>
>>
>> http://bugzilla.mozilla.org/show_bug.cgi?id=191739
>>
>
No, it hasn't been checkedin yet.
Hold off on builds if you disable localhost.
Mike
life...@xxvol.com
>Mike
My localhost works fine and I get the "not registered" message and the
disfunction.