On 24/10/2015 11:53 PM, Paul B. Gallagher wrote:
Mason83 wrote:
On 23/10/2015 03:42, Paul B. Gallagher wrote:
Probably a server issue; when I got the blank screen I did CTRL-U to
view the source code and that was blank, too. After a reload all was
well.
When that happened to me a few weeks ago, I used wget to grab
the webpage, and the server was timing out. Couldn't Mozilla
report an error instead of just displaying a blank page?!
It's rather confusing.
Agreed.
But it depends what the server is sending. If it really sends nothing or
doesn't respond, a software routine could detect that; you'd probably
get a 404 error or something. But if it sends something that you and I
perceive as blank that isn't quite blank -- say, a single space
character -- the software would not be able to analyze and evaluate that
as "not interesting enough."
Hang On!! The Mozilla server is too busy to send you the page that you
want, so you want the server to send you another, admittedly simpler,
web page instead!!
Does anyone else see the problem there?? ;-P
--
Daniel
User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:41.0) Gecko/20100101
SeaMonkey/2.38 Build identifier: 20150904215228
or
User agent: Mozilla/5.0 (X11; Linux x86_64; rv:41.0) Gecko/20100101
SeaMonkey/2.38 Build identifier: 20150903203501
_______________________________________________
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey
