• (disco)

    "Apparently, working for Google is stressful enough that even the servers have started drinking."

    That is possibly the best Error'd I've seen for a while. +1 Would laugh again.

  • (disco) in reply to HardwareGeek

    At first I thought it could be a Google Translate error, but now I'm wondering if that message isn't just a line of text entered by a user when creating a Google Form.

    Technically not an Error'd, more of an external @accalia.

  • (disco) in reply to JBert

    Could be, maybe, I guess. In any case, it made me actually laugh, which is more than most Error'ds do.

  • (disco) in reply to HardwareGeek

    Shorry for ruining your moment.


    Filed under: Sic

  • (disco)

    I regret to inform the authors that they have erred in their statements.

    HTTP 401:

    If the request already included Authorization credentials, then the 401 response indicates that authorization has been refused for those credentials.

    HTTP 403:

    The server understood the request, but is refusing to fulfill it.

    Therefore the premise stated in the article is incorrect, as the server is not stating login is required to logout, but rather that you are successfully logged in, but aren't allowed to view the page despite that. It is a fine detail, but an important one that the authors apparently missed. Wise users may note, however, that it is possible that the software in use, Disqus, has improperly placed a 403 where a 401 should have been used. This mistake, which I have seen in person too many times, is common amongst those who do not read the appropriate RFCs or reference materials prior to designing a web application. While this is a remote possibility, I still put forth that the article as stated misrepresents the facts and the meaning of HTTP 403. In short, the article, and likely the submitter himself, have failed to understand the difference between authorization and authentication. I state that this error should be rectified given the information we have now and invite any others to investigate further if Disqus is improperly using its status codes.

    Filed Under: :pendant: :badger: trolling

  • (disco) in reply to JBert

    Or just caused by someone hit the 'H' key of keyboard accidentially.

    Say, on workman keyboard layout, 'S' is near 'H' key. Maybe there is keyboard layout where 'E' is also near 'H'.

  • (disco) in reply to cheong
    cheong:
    Maybe there is keyboard layout where 'E' is also near 'H'.

    Must be the Canadian keyboard.

  • (disco) in reply to cheong

    Sounds legit...


    Filed under: A common typo

  • (disco) in reply to JBert
    JBert:
    At first I thought it could be a Google Translate error, but now I'm wondering if that message isn't just a line of text entered by a user when creating a Google Form.

    A drunk user at that.

  • (disco) in reply to JBert

    I just assumed it was Sean Connery day

  • (disco)

    "I need to log in to log out?"

    If it's Discourse, you'd never see that error, because you can't log out. Also jellypotato etc.

  • (disco) in reply to sloosecannon

    Two more likely explainations are:

    1. The httpd process is running as 'nobody' or 'webserver' and logout/index.htm is owned by root or another user and file permissions are causing a 403
    2. The lame-ass developer said 'href="/logout/"' when he meant to say 'href="/logout.htm"' and IndexOptions=None

    But yes, there are those who insist their ideas are better than RFC

  • (disco) in reply to Bananafish
    Bananafish:
    But yes, there are those who insist their ideas are better than RFC

    Well of course. It's only a request for comments, after all.

  • (disco) in reply to MattSmucker
    MattSmucker:
    I just assumed it was Sean Connery day

    That's what I had figured.

    [image]
  • (disco) in reply to MattSmucker
    MattSmucker:
    Sean Connery
    The only person who can play a Spaniard and a Russian with the same accent and get away with it :smile:
  • (disco) in reply to chubertdev

    How would you pronounce an 'h' before a 'd'?

    If I try one more time my kids will think I'm losing it.

  • (disco) in reply to sloosecannon
    sloosecannon:
    This mistake, which I have seen in person too many times, is common amongst those who do not read the appropriate RFCs or reference materials prior to designing a web application.

    Silly developers, not reading lengthy boring documents to find out which arbitrary code they should use. Don't they know that millions of applications crash every year due to using HTTP code 403 instead of 401?

  • (disco) in reply to chubertdev

    You're still around?!

  • (disco)

    Respondents should NOT see the page, but I did, unfortunately, because the word "Sesstion" hurts my eyes.

  • (disco) in reply to JBert
    JBert:
    Filed under: SicHic

    FTFY :rofl:

  • (disco) in reply to cheong
    cheong:
    Maybe there is keyboard layout where 'E' is also near 'H'.

    I can think of at least one :wink:

  • (disco)

    "Oh crap, now I've seen it. Now what?" wrote Quentin G.

    Well, if you've seen / heard something that you shouldn't have, I think there is only one course of action left open to Them®

    It will be messy, but quick. RIP

  • (disco)

    First of all, I could see it Photoshop saying something like "Unable to open .psd files" but no, it not only knows it can't open the file, but it has steps included so it can say it is an "Adobe Photoshop file" it can't open. So they went to all that trouble and they can't say, "...because the file is corrupt"?

    Anyway.

    I had a conjecture that some broken code was replacing all "s" by "sh". But the "esd" at the end blew that conjecture all to pieces...

  • (disco) in reply to CoyneTheDup

    You know the description of the file type comes from the OS not Photoshop, right?

  • (disco) in reply to RaceProUK

    It is just an Error'd article…

  • (disco) in reply to dkf

    I can't be pendantic on WTDWTF anymore? :cry:

  • (disco) in reply to RaceProUK

    Of course you can! It just won't stop the rest of us from also being pendantic…

  • (disco) in reply to Bananafish

    I find it hard to believe that Disqus is directly serving HTML files from the httpd process, instead of using an application server to handle their requests.

    The explanation I find most likely is that they simply have a generic layer that verifies the authentication for marked paths/controller methods, the developer implementing /logout marked it as requiring a minimum authorization level of a basic user (since you can't logout anonymous users), and so the generic layer returned Forbidden since the user did not have that level.

  • (disco) in reply to loose
    loose:
    I can think of at least one

    In the standard Russian keyboard layout (probably true of other non-Latin alphabets as well) very common letter pairs seem to be close to one another, e.g. пр, вы, он. Perhaps this was typed on a Canadian keyboard where E and H are next to one another. :confused:

  • (disco) in reply to sloosecannon

    You forgot the dickweed part.

  • (disco) in reply to abarker

    Meh. Wasn't trying too hard...

  • (disco) in reply to cheong

    Maybe the Crotian keyboard ;)

  • (disco) in reply to Masaaki_Hosoi

    Humm... no. :stuck_out_tongue:

    http://www.microsoft.com/resources/msdn/goglobal/keyboards/kbdcr.html

  • (disco) in reply to Masaaki_Hosoi
    Masaaki_Hosoi:
    Maybe the Crotian keyboard

    Paging @Onyx...

  • (disco) in reply to kupfernigk
    kupfernigk:
    (probably true of other non-Latin alphabets as well) very common letter pairs seem to be close to one another

    Probably true for any layout which was developed after typewriter entry speed restrictions were no longer worth a serious consideration.

  • (disco) in reply to obeselymorbid
    obeselymorbid:
    Probably true for any layout which was developed after typewriter entry speed restrictions were no longer worth a serious consideration.

    I'm not 100% convinced of the explanation for qwertyuiop being collision avoidance. A different explanation I heard was so that a design patent could be issued, preventing other manufacturers from using the same keyboard layout even if they invented a typewriter that did not infringe on the functional patents.

  • (disco) in reply to kupfernigk

    Quick skimming of wiki article seems to confirm my previous recollection that the main reason for QWERTY was jam avoidance.

  • (disco) in reply to obeselymorbid
    obeselymorbid:
    Quick skimming of wiki article seems to confirm my previous recollection that the main reason for QWERTY was jam avoidance.

    Not entire uncontroversial that, though.

    http://www.smithsonianmag.com/arts-culture/fact-of-fiction-the-legend-of-the-qwerty-keyboard-49863249/?no-ist

    the mechanics of the typewriter did not influence the keyboard design. Rather, the QWERTY system emerged as a result of how the first typewriters were being used. Early adopters and beta-testers included telegraph operators who needed to quickly transcribe messages. However, the operators found the alphabetical arrangement to be confusing and inefficient for translating morse code.

  • (disco) in reply to obeselymorbid
    obeselymorbid:
    Quick skimming of wiki article

    The only way to be sure with Wikipedia is to ignore the article and check the references. And even then be very careful because some editors plant fake articles on other sites so they can reference them. I find with Wikipedia that the more I know about a subject the less I tend to agree with the article on it, and I extrapolate from there.

Leave a comment on “Crotia? Slovania? DO NOT USE!”

Log In or post as a guest

Replying to comment #:

« Return to Article