Should I just code in a work-around? If the Referer is /post then consider that total bullshit, and ignore? 🤔

@prologic@twtxt.net I was wondering if my reverse proxy could cause something but it’s pretty standard…

server {

    listen 80;
    server_name we.loveprivacy.club;

    location / {
            return 301 https://$host$request_uri;
            <a href="https://txt.sour.is/search?tag=proxy_pass">#proxy_pass</a> http://127.0.0.1:8000;
    }

}
server {

    listen 443 ssl http2;
    server_name we.loveprivacy.club;

    ssl_certificate /etc/letsencrypt/live/we.loveprivacy.club/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/we.loveprivacy.club/privkey.pem;

    client_max_body_size 8M;

    location / {
            proxy_pass http://127.0.0.1:8000;
    }

}

@prologic@twtxt.net Woops my blockquote got mangled but you get the gist haha

Okay just pushed:

* aa2f3ae9 - (HEAD -> main, origin/main) Workaround for this invalid Referer BS (6 seconds ago) <James Mills>

@eldersnake@we.loveprivacy.club Looks legit 👌

@prologic@twtxt.net Fix works!

@eldersnake@we.loveprivacy.club Fuck’n hell 🤣 This has to be a browser bug!

What browser and version is this btw? Not sure if you mentioned?

@prologic@twtxt.net Firefox 126.0.1 is my primary

@eldersnake@we.loveprivacy.club I just installed 127.0.1 (64-bit) tonight and tested and it worked just fine. Try upgrading and roll that commit back and see if it still repros? 🤔 I’m almost willing to bet this is a bug 🐛

@prologic@twtxt.net It’s weird though cos I could reproduce it on any of my browsers on either my laptop or phone 🤔

Test

EDIT: Okay, convo works properly now at least

@eldersnake@we.loveprivacy.club Good good 👍