Sunday

Chris M. got a 406 error yesterday. Has this happened to anyone else?

Notice I fixed the archive list on the right side panel? I don’t know how it happened. I have my idiot assistant working on a new layout. If the blog disappears sometime this week, blame Frau Grace.

Uh oh! Trouble with Bobo. From 2013…

This entry was posted in Uncategorized. Bookmark the permalink.

8 Responses to Sunday

  1. Tom B says:

    No 406 error for me, works fine.

  2. S maltophilia says:

    Got 406 and blank images.

    Firefox + Win 10.

  3. Victor says:

    For a week— Error 406 on my old MacBook. I guess it depends on the OS/browser you’re using…

  4. Peter says:

    Apple sneaked in an undocumented “security update” under cover of its updates to iPadOS 14.5 and iTunes for macOS. This caused the 406 “error” on Bud’s website on an iPad which had not been updated and which was miraculously cured by installing the 14.5 update. Apple’s error message egregiously tried to place the blame on website owners. The iTunes update on a Mac also causes problems with loading some previously working web addresses which Apple now claims are not meeting some “protocol” – presumably one they have just invented themselves?

    • Bud Grace says:

      Thanks to you and all.
      Apple is bad about screwing up your systems with updates. I’ll post that people should update their operating systems. Also I’ll check my plugins.

  5. AndyW says:

    Worked fine for me – using Safari.

  6. Scott says:

    Very interesting, I’ve never even seen a 406 error before myself!

    https://airbrake.io/blog/http-errors/406-not-acceptable

    > The 406 Not Acceptable is an HTTP response status code indicating that the client has requested a response using Accept- headers that the server is unable to fulfill. This is typically a result of the user agent (i.e. browser) specifying an acceptable character set (via Accept-Charset), language (via Accept-Language), and so forth that should be responded with, and the server being unable to provide such a response.

    I wonder if this triggers any “aha!” for Chris or Victor.

    Maybe if you say “the response MUST be in Spanish” most servers just ignore that if impossible, but the recent upgrades put the blog in some more strict mode where it takes the requirements seriously and returns 406 if it can’t rather than just say respond in English instead.

    • Scott says:

      Update: Got this by accessing via curl:

      Error 406 – Not AcceptableError 406 – Not AcceptableGenerally a 406 error is caused because a request has been blocked by Mod Security. If you believe that your request has been blocked by mistake please contact the web site owner.

      So this isn’t the correct use of 406, there’s some sort of security plugin activated that is trying to detect hackers or something by analyzing headers and it’s decided that some valid connections are not valid.

Leave a Reply

Your email address will not be published. Required fields are marked *