GNU social JP
  • FAQ
  • Login
GNU social JPは日本のGNU socialサーバーです。
Usage/ToS/admin/test/Pleroma FE
  • Public

    • Public
    • Network
    • Groups
    • Featured
    • Popular
    • People

Conversation

Notices

  1. Embed this notice
    Annika Backstrom (annika@xoxo.zone)'s status on Friday, 22-Aug-2025 20:02:13 JST Annika Backstrom Annika Backstrom

    Anyone know how I can force nginx to reply with a 410 (or some other code) for a POST request?

    I killed my Pixelfed server a while ago. I'm returning 410 from nginx:

    ```
    error_page 410 @gone;

    location @gone {
    rewrite . /410.html break;
    }

    location / {
    return 410;
    }
    ```

    GET requests return 410, but POST requests return a 405. xoxo.zone as well as many other servers don't register this as a "failure" so it's still being hit all these months later. Can I force a different reply?

    In conversation about 2 days ago from xoxo.zone permalink

    Attachments

    1. Domain not in remote thumbnail source whitelist: xoxo-media.sfo2.cdn.digitaloceanspaces.com
      XOXO Zone
      A community space for attendees and speakers of the XOXO Festival, held in Portland, Oregon.
    • Embed this notice
      Annika Backstrom (annika@xoxo.zone)'s status on Friday, 22-Aug-2025 20:56:13 JST Annika Backstrom Annika Backstrom
      in reply to
      • Ellie 🐍 🎄:trans_heart:​

      @noelle Ah I will give that a try later. What I have is mostly working (it shows the generic 410 if you directly hit the 410.html, which is odd) but I wonder if it could be less lines

      In conversation about 2 days ago permalink
    • Embed this notice
      Ellie 🐍 🎄:trans_heart:​ (noelle@chat.noelle.codes)'s status on Friday, 22-Aug-2025 20:56:14 JST Ellie 🐍 🎄:trans_heart:​ Ellie 🐍 🎄:trans_heart:​
      in reply to

      @annika Looks like you're heading toward a solution just as I found your post. :) As far as I know, nginx doesn't allow POST requests to static sites (i.e. not proxying to a server running on another port/system, fastcgi, etc.), which is why it's bouncing the POST requests before they get to your location handler. Setting a custom error_page 405 =410 $uri should, I think, resolve the issue, but I just woke up so take it with a grain of salt. :)

      In conversation about 2 days ago permalink
    • Embed this notice
      Annika Backstrom (annika@xoxo.zone)'s status on Saturday, 23-Aug-2025 01:52:37 JST Annika Backstrom Annika Backstrom
      in reply to
      • Eli the Bearded

      @elithebearded I turned on FETCH_REPLIES_ENABLED and it's been a godsend. It sometimes requires a reload (if replies weren't fetched before you visited the post) but that's easier than visiting the remote server at least https://blog.gelbphoenix.de/introducing-mastodons-fetch-replies-feature/

      In conversation about 2 days ago permalink

      Attachments

      1. Domain not in remote thumbnail source whitelist: blog.gelbphoenix.de
        Introducing Mastodon's “Fetch Replies” Feature
        Discover Mastodon’s experimental Fetch Replies feature: how it enriches conversations across instances, boosts context, and enhances your experience.
    • Embed this notice
      Eli the Bearded (elithebearded@fed.qaz.red)'s status on Saturday, 23-Aug-2025 01:52:40 JST Eli the Bearded Eli the Bearded
      in reply to

      @annika

      I can't believe it is August 2025 and I still have to go the original server to see *any* replies to a boosted message.

      Glad you got that solved and I'm taking notes

      In conversation about 2 days ago permalink

Feeds

  • Activity Streams
  • RSS 2.0
  • Atom
  • Help
  • About
  • FAQ
  • TOS
  • Privacy
  • Source
  • Version
  • Contact

GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.

Creative Commons Attribution 3.0 All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.