Re: Website problems
On Sun, 22 Nov 2009 15:10:12 -0500, Paul B. Gallagher wrote: Benoit Renard wrote: Paul B. Gallagher wrote: Hard to know /what/ this is -- an embedded graphic in the XHTML code??? input type=hidden name=__VIEWSTATE id=__VIEWSTATE value= [51,256 characters of alphabet soup snipped] / Hell, it took IE four minutes just to /display/ all this crap in Notepad. It's ASP state information for the ASP server. Fifty K of it? Is this normal? Hello! This is Microsoft (Bloat'R'Us) we are talking about. Phil -- Philip Chee phi...@aleytys.pc.my, philip.c...@gmail.com http://flashblock.mozdev.org/ http://xsidebar.mozdev.org Guard us from the she-wolf and the wolf, and guard us from the thief, oh Night, and so be good for us to pass. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Website problems
On 11/23/2009 07:13 AM, David E. Ross wrote: On 11/22/2009 11:38 PM, Cedar wrote: Wow! You guys are fantastic! That actually workedI can even click on the e-mail newsletter links and get there now! Holy Cow! (haha) But now, should I leave this new string in about:config permanently? Are there any possible circumstance/websites where this change may cause problems? Thanks much. I would definitely NOT spoof permanently. Permanent spoofing tells the Web site developers that everything is okay when that is not true. Then, when someone complains that their site does not work with SeaMonkey, they say that no one uses SeaMonkey to access their site. Says David while using Thunderbird :-) The reason for the 'NOT Firefox/someversion' has been discussed quite a lot in the past. The conclusion was to add it in that manner so that SeaMonkey would be recongnized, while at the same time by passing the Fx sniffing issue. If someone is gathering stats on their site they will/should see the SeaMonkey in the UA string. Install an extension for spoofing. There are several. They have an editable list of browsers whose user agent strings you can select, including returning to your actual browser's string (turning off spoofing). They also automatically turn off spoofing when you terminate SeaMonkey. One popular extension for spoofing is User Agent Switcher at http://chrispederick.com/work/user-agent-switcher/. I prefer PrefBar at http://prefbar.mozdev.org/ because of its other features unrelated to spoofing. I very much recommend prefbar as well. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Website problems
On 11/23/2009 1:45 PM, NoOp wrote [in part]: On 11/23/2009 07:13 AM, I previously wrote [also in part]: I would definitely NOT spoof permanently. Permanent spoofing tells the Web site developers that everything is okay when that is not true. Then, when someone complains that their site does not work with SeaMonkey, they say that no one uses SeaMonkey to access their site. Says David while using Thunderbird :-) I use Thunderbird as my newsgroup application because, when I switch SeaMonkey profiles, I don't want to lose my current newsgroup session. The reason for the 'NOT Firefox/someversion' has been discussed quite a lot in the past. The conclusion was to add it in that manner so that SeaMonkey would be recongnized, while at the same time by passing the Fx sniffing issue. If someone is gathering stats on their site they will/should see the SeaMonkey in the UA string. You assume that some human sees the logs. I'm only guessing, but I think that very rarely happens. When I spoof, I use the following UA string: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.4) Gecko/20091017 SeaMonkey/2.0, NOT Firefox/3.5.3 The processing that summarizes the logs for human use is very likely to be similar to the processing that makes a server think I'm using Firefox. -- David E. Ross http://www.rossde.com/ Go to Mozdev at http://www.mozdev.org/ for quick access to extensions for Firefox, Thunderbird, SeaMonkey, and other Mozilla-related applications. You can access Mozdev much more quickly than you can Mozilla Add-Ons. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Website problems
Would somebody mind telling me what this browser sniffing thing is all about? ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Website problems
On 11/22/2009 12:10 AM, Cedar wrote: Would somebody mind telling me what this browser sniffing thing is all about? See my http://www.rossde.com/internet/Webdevelopers.html#sniff. -- David E. Ross http://www.rossde.com/ Go to Mozdev at http://www.mozdev.org/ for quick access to extensions for Firefox, Thunderbird, SeaMonkey, and other Mozilla-related applications. You can access Mozdev much more quickly than you can Mozilla Add-Ons. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Website problems
On 11/22/2009 08:55 AM, David E. Ross wrote: On 11/22/2009 12:10 AM, Cedar wrote: Would somebody mind telling me what this browser sniffing thing is all about? See my http://www.rossde.com/internet/Webdevelopers.html#sniff. @Cedar: And to modify your UA: In the address bar, type in: about:config. Once its up, right click on any entry and select New, String, and enter the following in the first box: general.useragent.extra.firefox then in the next box enter: NOT Firefox/3.5 That's it. Now try your http://www.cattlenetwork.com/ link. Also see: https://developer.mozilla.org/en/Browser_Detection_and_Cross_Browser_Support Note: you can send this link to cattlenetwork.com ask that the sniff on 'gecko' instead. Contact info page shows: CattleNetwork.com 10901 W. 84th Terrace Lenexa, KS 66214 913-438-8700 i...@cattlenetwork.com Call them, email them, write them. Let them know that their code is preventing you from using their site without browser spoofing. Point them to this thread on Google Groups: http://groups.google.com/group/mozilla.support.seamonkey/browse_thread/thread/977bcb4c1a0e3566?hl=en http://www.mozilla.org/projects/tech-evangelism/ http://www.google.com/webhp?complete=0#complete=0hl=enq=gecko+%2Bbrowser+sniffing ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Website problems
David E. Ross wrote: The page has 762 XHTML errors and 9 (or more) CSS errors. While many different browsers are designed to attempt to render pages containing errors, there are limits beyond which such attempts cannot succeed. They are designed to make such attempts if the pages are HTML. Properly sent XHTML, though, is a different story. They must fail to render those pages with a cryptic error message if the document is not well-formed. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Website problems
Paul B. Gallagher wrote: Hard to know /what/ this is -- an embedded graphic in the XHTML code??? input type=hidden name=__VIEWSTATE id=__VIEWSTATE value= [51,256 characters of alphabet soup snipped] / Hell, it took IE four minutes just to /display/ all this crap in Notepad. It's ASP state information for the ASP server. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Website problems
Benoit Renard wrote: Paul B. Gallagher wrote: Hard to know /what/ this is -- an embedded graphic in the XHTML code??? input type=hidden name=__VIEWSTATE id=__VIEWSTATE value= [51,256 characters of alphabet soup snipped] / Hell, it took IE four minutes just to /display/ all this crap in Notepad. It's ASP state information for the ASP server. Fifty K of it? Is this normal? -- War doesn't determine who's right, just who's left. -- Paul B. Gallagher ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Website problems
Wow! You guys are fantastic! That actually workedI can even click on the e-mail newsletter links and get there now! Holy Cow! (haha) But now, should I leave this new string in about:config permanently? Are there any possible circumstance/websites where this change may cause problems? Thanks much. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Website problems
Cedar wrote: When I go to this website with SM 2: www.cattlenetwork.com, I get the following error message: XML Parsing Error: mismatched tag. Expected: /meta. (snip) Any ideas what this might be about? The website is using XHTML, which requires it to be well-formed. But it's not well-formed, so parsing it fails with that error message. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Website problems
Cedar wrote: When I go to this website with SM 2: www.cattlenetwork.com, I get the following error message: XML Parsing Error: mismatched tag. Expected: /meta. Location: http://www.cattlenetwork.com/ Line Number 36, Column 449:meta name=google-site-verification content=OaEYk1WjScjIOpwuOyxCWyPJhJk0F9byX3q7s6cgtOQ /link href=/App_Themes/Theme/CSSHandler.axd?page=JGiJdDpvd5mqQf4kon3jcktmlugEgTLeXrO97BQ6_M0zuv2f1x9gDI74u0-Lq79G0amp;t=-enbEn1smA5dIAmLvd63r98KRSZX9FhMgM3HF72lIjk1amp;p=11Ir3EFxTdMkv009Q5tOcQ2 type=text/css rel=stylesheet /meta name=description content=Up To The Minute Beef Cattle News amp; Information Ranging From Ranch To Retail //head ^ Any ideas what this might be about? If someone else would be so kind as to try this website and see if you get the same would be appreciated. Yes, I get it too, with SM 1.1.16. The point of the message is that if you have a meta tag you must also have a /meta tag (that's what mismatched means -- it's like having an opening parenthesis without a closing parenthesis). When the parser reaches the /head tag, it gives up. Not your fault, not your browser's fault, though I suppose some might say the browser should overlook this error. Internet Exploiter does. -- War doesn't determine who's right, just who's left. -- Paul B. Gallagher ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Website problems
Cedar: [www.cattlenetwork.com] Any ideas what this might be about? If someone else would be so kind as to try this website and see if you get the same would be appreciated. Well, using http://validator.w3.org/: Errors found while checking this document as XHTML 1.0 Transitional! Result: 762 Errors, 239 warning(s) ;) Hartmut ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Website problems
On 11/21/2009 4:27 AM, Benoit Renard wrote: Cedar wrote: When I go to this website with SM 2: www.cattlenetwork.com, I get the following error message: XML Parsing Error: mismatched tag. Expected: /meta. (snip) Any ideas what this might be about? The website is using XHTML, which requires it to be well-formed. But it's not well-formed, so parsing it fails with that error message. The page has 762 XHTML errors and 9 (or more) CSS errors. While many different browsers are designed to attempt to render pages containing errors, there are limits beyond which such attempts cannot succeed. -- David E. Ross http://www.rossde.com/ Go to Mozdev at http://www.mozdev.org/ for quick access to extensions for Firefox, Thunderbird, SeaMonkey, and other Mozilla-related applications. You can access Mozdev much more quickly than you can Mozilla Add-Ons. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Website problems
/Paul B. Gallagher/: Cedar wrote: When I go to this website with SM 2: www.cattlenetwork.com, I get the following error message: XML Parsing Error: mismatched tag. Expected: /meta. (...) Any ideas what this might be about? If someone else would be so kind as to try this website and see if you get the same would be appreciated. Yes, I get it too, with SM 1.1.16. The point of the message is that if you have a meta tag you must also have a /meta tag (that's what mismatched means -- it's like having an opening parenthesis without a closing parenthesis). When the parser reaches the /head tag, it gives up. In HTML the META element doesn't have an end tag. However they serve the page explicitly specifying 'Content-Type: application/xhtml+xml' which makes the browser use an XML parser. Seems they sniff on the 'User-Agent' request header and serve different 'Content-Type' depending on the browser, as I don't get problem using Firefox 3.5, Safari 4 and Opera 10. Not your fault, not your browser's fault, though I suppose some might say the browser should overlook this error. Internet Exploiter does. Internet Explorer doesn't understand XHTML. It parses it as regular tag-soup HTML. -- Stanimir ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Website problems
Stanimir Stamenkov wrote: c /Paul B. Gallagher/: Cedar wrote: When I go to this website with SM 2: www.cattlenetwork.com, I get the following error message: XML Parsing Error: mismatched tag. Expected: /meta. (...) Any ideas what this might be about? If someone else would be so kind as to try this website and see if you get the same would be appreciated. Yes, I get it too, with SM 1.1.16. The point of the message is that if you have a meta tag you must also have a /meta tag (that's what mismatched means -- it's like having an opening parenthesis without a closing parenthesis). When the parser reaches the /head tag, it gives up. In HTML the META element doesn't have an end tag. However they serve the page explicitly specifying 'Content-Type: application/xhtml+xml' which makes the browser use an XML parser. Seems they sniff on the 'User-Agent' request header and serve different 'Content-Type' depending on the browser, as I don't get problem using Firefox 3.5, Safari 4 and Opera 10. Yes, Internet Exploiter 8 is told it's text/html, but SeaMonkey is not. How about that. Not your fault, not your browser's fault, though I suppose some might say the browser should overlook this error. Internet Exploiter does. Internet Explorer doesn't understand XHTML. It parses it as regular tag-soup HTML. Hard to know /what/ this is -- an embedded graphic in the XHTML code??? input type=hidden name=__VIEWSTATE id=__VIEWSTATE value= [51,256 characters of alphabet soup snipped] / Hell, it took IE four minutes just to /display/ all this crap in Notepad. -- War doesn't determine who's right, just who's left. -- Paul B. Gallagher ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Website problems
Hartmut Figge wrote: Cedar: [www.cattlenetwork.com] Any ideas what this might be about? If someone else would be so kind as to try this website and see if you get the same would be appreciated. Well, using http://validator.w3.org/: Errors found while checking this document as XHTML 1.0 Transitional! Result: 762 Errors, 239 warning(s) ;) Hartmut Wow! Thanks much everybody! ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Website problems
On 11/20/2009 11:34 PM, Cedar wrote: When I go to this website with SM 2: www.cattlenetwork.com, I get the following error message: XML Parsing Error: mismatched tag. Expected: /meta. Location: http://www.cattlenetwork.com/ Line Number 36, Column 449:meta name=google-site-verification content=OaEYk1WjScjIOpwuOyxCWyPJhJk0F9byX3q7s6cgtOQ /link href=/App_Themes/Theme/CSSHandler.axd?page=JGiJdDpvd5mqQf4kon3jcktmlugEgTLeXrO97BQ6_M0zuv2f1x9gDI74u0-Lq79G0amp;t=-enbEn1smA5dIAmLvd63r98KRSZX9FhMgM3HF72lIjk1amp;p=11Ir3EFxTdMkv009Q5tOcQ2 type=text/css rel=stylesheet /meta name=description content=Up To The Minute Beef Cattle News amp; Information Ranging From Ranch To Retail //head ^ Any ideas what this might be about? If someone else would be so kind as to try this website and see if you get the same would be appreciated. Thanks. Works for me. However note that I have the 'NOT Firefox' in my UI: # Build identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.4) Gecko/20091017 NOT Firefox/3.5 Lightning/1.0pre SeaMonkey/2.0 Let's take it out try again to see if they are browser sniffing... Build identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.4) Gecko/20091017 Lightning/1.0pre SeaMonkey/2.0 Whoops... that get's the same error as your's. Put the 'NOT Firefox/3.5' back in it now works. So they *are* browser sniffing. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Website problems
On 11/21/2009 8:08 AM, Stanimir Stamenkov wrote: /Paul B. Gallagher/: Cedar wrote: When I go to this website with SM 2: www.cattlenetwork.com, I get the following error message: XML Parsing Error: mismatched tag. Expected: /meta. (...) Any ideas what this might be about? If someone else would be so kind as to try this website and see if you get the same would be appreciated. Yes, I get it too, with SM 1.1.16. The point of the message is that if you have a meta tag you must also have a /meta tag (that's what mismatched means -- it's like having an opening parenthesis without a closing parenthesis). When the parser reaches the /head tag, it gives up. In HTML the META element doesn't have an end tag. However they serve the page explicitly specifying 'Content-Type: application/xhtml+xml' which makes the browser use an XML parser. Seems they sniff on the 'User-Agent' request header and serve different 'Content-Type' depending on the browser, as I don't get problem using Firefox 3.5, Safari 4 and Opera 10. Not your fault, not your browser's fault, though I suppose some might say the browser should overlook this error. Internet Exploiter does. Internet Explorer doesn't understand XHTML. It parses it as regular tag-soup HTML. Hmm. The server is sniffing for the UA string. When I spoof Firefox 3.5, I can readily view the page. When I don't spoof at all, I see Cedar's original problem. The interesting thing is that, when I send the URI to the W3C validator at http://validator.w3.org/, it reports 762 XHTML errors. When I spoof Firefox 3.5, view and copy the source, and paste it into the W3C validator, it reports 787 XHTML errors, 25 more than for just the URI. All this merely reaffirms the old saying: Garbage in equals garbage out. I might submit a Tech Evangelism bug report. -- David E. Ross http://www.rossde.com/ Go to Mozdev at http://www.mozdev.org/ for quick access to extensions for Firefox, Thunderbird, SeaMonkey, and other Mozilla-related applications. You can access Mozdev much more quickly than you can Mozilla Add-Ons. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Website problems
NoOp wrote: On 11/20/2009 11:34 PM, Cedar wrote: When I go to this website with SM 2: www.cattlenetwork.com, I get the following error message: XML Parsing Error: mismatched tag. Expected:/meta. Location: http://www.cattlenetwork.com/ Line Number 36, Column 449:meta name=google-site-verification content=OaEYk1WjScjIOpwuOyxCWyPJhJk0F9byX3q7s6cgtOQ /link href=/App_Themes/Theme/CSSHandler.axd?page=JGiJdDpvd5mqQf4kon3jcktmlugEgTLeXrO97BQ6_M0zuv2f1x9gDI74u0-Lq79G0amp;t=-enbEn1smA5dIAmLvd63r98KRSZX9FhMgM3HF72lIjk1amp;p=11Ir3EFxTdMkv009Q5tOcQ2 type=text/css rel=stylesheet /meta name=description content=Up To The Minute Beef Cattle Newsamp; Information Ranging From Ranch To Retail //head ^ Any ideas what this might be about? If someone else would be so kind as to try this website and see if you get the same would be appreciated. Thanks. Works for me. However note that I have the 'NOT Firefox' in my UI: # Build identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.4) Gecko/20091017 NOT Firefox/3.5 Lightning/1.0pre SeaMonkey/2.0 Let's take it out try again to see if they are browser sniffing... Build identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.4) Gecko/20091017 Lightning/1.0pre SeaMonkey/2.0 Whoops... that get's the same error as your's. Put the 'NOT Firefox/3.5' back in it now works. So they *are* browser sniffing. was able to go to it with no problem. I use on a Mac, OSX.4.11 and Flash 10 plugin No alteration of my user agent. (Mas OSX 4.11 SM2) -- Phillip M. Jones, C.E.T.If it's Fixed, Don't Break it http://www.phillipmjones.net http://www.vpea.org mailto:pjon...@kimbanet.com ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Website problems
On 11/21/2009 5:21 PM, David E. Ross wrote: On 11/21/2009 8:08 AM, Stanimir Stamenkov wrote: /Paul B. Gallagher/: Cedar wrote: When I go to this website with SM 2: www.cattlenetwork.com, I get the following error message: XML Parsing Error: mismatched tag. Expected: /meta. (...) Any ideas what this might be about? If someone else would be so kind as to try this website and see if you get the same would be appreciated. Yes, I get it too, with SM 1.1.16. The point of the message is that if you have a meta tag you must also have a /meta tag (that's what mismatched means -- it's like having an opening parenthesis without a closing parenthesis). When the parser reaches the /head tag, it gives up. In HTML the META element doesn't have an end tag. However they serve the page explicitly specifying 'Content-Type: application/xhtml+xml' which makes the browser use an XML parser. Seems they sniff on the 'User-Agent' request header and serve different 'Content-Type' depending on the browser, as I don't get problem using Firefox 3.5, Safari 4 and Opera 10. Not your fault, not your browser's fault, though I suppose some might say the browser should overlook this error. Internet Exploiter does. Internet Explorer doesn't understand XHTML. It parses it as regular tag-soup HTML. Hmm. The server is sniffing for the UA string. When I spoof Firefox 3.5, I can readily view the page. When I don't spoof at all, I see Cedar's original problem. The interesting thing is that, when I send the URI to the W3C validator at http://validator.w3.org/, it reports 762 XHTML errors. When I spoof Firefox 3.5, view and copy the source, and paste it into the W3C validator, it reports 787 XHTML errors, 25 more than for just the URI. All this merely reaffirms the old saying: Garbage in equals garbage out. I might submit a Tech Evangelism bug report. This is now bug #530359 at https://bugzilla.mozilla.org/show_bug.cgi?id=530359. -- David E. Ross http://www.rossde.com/ Go to Mozdev at http://www.mozdev.org/ for quick access to extensions for Firefox, Thunderbird, SeaMonkey, and other Mozilla-related applications. You can access Mozdev much more quickly than you can Mozilla Add-Ons. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Website problems
When I go to this website with SM 2: www.cattlenetwork.com, I get the following error message: XML Parsing Error: mismatched tag. Expected: /meta. Location: http://www.cattlenetwork.com/ Line Number 36, Column 449:meta name=google-site-verification content=OaEYk1WjScjIOpwuOyxCWyPJhJk0F9byX3q7s6cgtOQ /link href=/App_Themes/Theme/CSSHandler.axd?page=JGiJdDpvd5mqQf4kon3jcktmlugEgTLeXrO97BQ6_M0zuv2f1x9gDI74u0-Lq79G0amp;t=-enbEn1smA5dIAmLvd63r98KRSZX9FhMgM3HF72lIjk1amp;p=11Ir3EFxTdMkv009Q5tOcQ2 type=text/css rel=stylesheet /meta name=description content=Up To The Minute Beef Cattle News amp; Information Ranging From Ranch To Retail //head ^ Any ideas what this might be about? If someone else would be so kind as to try this website and see if you get the same would be appreciated. Thanks. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
