41–50 of 78 posts
I feel bad the lemmings splat and die :/
You could write a script to save them all!
var saveTheirSouls = function() { $('img').trigger('mouseover'); setTimeout( function() { if ($('img').length > 1) { return saveTheirSouls() } else { return false; } }, 1000); }; saveTheirSouls();
One of my favourite 404 pages was this: http://www.homestarrunner.com/systemisdown.html
Earlier quoted context omitted.
window.setInterval(function() { $('img').mouseover(); }, 500); So you can catch the ones that haven't been created yet.
$('img').live('mouseover', function() {}); Same, but nicer, listens to mouseover events on img elements that may not exist yet. Then again, this will - if I understand correctly - cause the event to bubble up in the DOM until it reaches the root element, where jquery's live callback handler will check what element the event took place on and invoke that callback.
winCount = count = 404; while ($('img').length > 0) { $('img').remove(); }
If the content has moved, I should get a 30x redirect. If the server has a way of guessing what I wanted, I should get 300 Multiple Choices. If the server knows that what I'm looking for isn't anywhere, I should get 410 Gone. 404 is supposed to mean that the server has no idea what I'm looking for, no idea how to find it, no idea where to look.
In that case, I don't want a page to load. I don't want a tab to open. I definitely don't want to download a Flash game, or a 500kb JPEG, or infinity many Lemming images. I just want my browser to mark that link as dead and let me know in as unobtrusive a way as possible, "Hey, you clicked on some bullshit!" Let me either search the domain or click something else.
Not to rag on creative 404s, and I know it's a bit of a pipe dream. Just a peeve of mine.
Earlier quoted context omitted.
That's not not a 404 page (missing page). It seems like it's supposed to be a 500 page (server error) or 503 page (unavailable) but it incorrectly returns a 200 status which means everything is OK. Edit: Corrected the 50X error information thanks to the responses below.
It is correct for a request for a page named "error" to result in a 200 OK status meaning that the page named "error" was successfully retrieved. It would not be correct for a request for a page named "error" to return 404 Not Found if the page named "error" was retrieved successfully. It would also not be correct for a request for a page that does not exist to return the page named "error" with a 200 OK status.
2) I made an assumption, based on the context, that this page was serving a role that is used when the server is overloaded or otherwise unavailable. In that case, this page should not be serving a 200 status, it should be serving a 50X response.
Now, it's possible that this page is just a demonstration of the error that would normally be produced when the website is unavailable. In that case, sure, 200 status is proper since it's not meant to actually be the literal error page which is served when the site has gone down. It's also possible the page has logic in it to serve 200 error when requested directly and 50X when the server is down.
In really, I bet this page is served as-is when the website is unavailable and sends a 200 error. It's difficult to know whether or not this is true until we see a real problem with the server.
MutationObserver(function(event) {
$(event[0].addedNodes[0]).mouseover();
}).observe($('body')[0], {childList: true});
$('img').mouseover();Earlier quoted context omitted.
It is correct for a request for a page named "error" to result in a 200 OK status meaning that the page named "error" was successfully retrieved. It would not be correct for a request for a page named "error" to return 404 Not Found if the page named "error" was retrieved successfully. It would also not be correct for a request for a page that does not exist to return the page named "error" with a 200 OK status.
1) This page in no way is related to page missing (404). My response that it is not a 404 page is correct. This page has nothing to do with 404 error. 2) I made an assumption, based on the context, that this page was serving a role that is used when the server is overloaded or otherwise unavailable. In that case, this page should not be serving a 200 status, it should be serving a 50X response. Now, it's possible tha…
I've said it before, but: What's the deal with 404 pages? If the content has moved, I should get a 30x redirect. If the server has a way of guessing what I wanted, I should get 300 Multiple Choices. If the server knows that what I'm looking for isn't anywhere, I should get 410 Gone. 404 is supposed to mean that the server has no idea what I'm looking for, no idea how to find it, no idea where to look. In that case, I…