Hmm…

Jun 19 23:31:38 yarn_init.sh[61567]: [yarnd] 2024/06/19 23:31:38 (127.0.0.1:40254) “POST /post HTTP/
1.0” 200 0 3.402208ms
[…]

Jun 19 23:31:39 yarn_init.sh[61567]: [yarnd] 2024/06/19 23:31:39 (127.0.0.1:40262) “GET /post HTTP/1.0” 404 729 123.474001ms

@eldersnake@we.loveprivacy.club Holy fuck?! That’s unpossible?!

Let’s focus on this ☝️ how in da fuq is this happenning?!

There is only one explanation for this… Lemme see…

The only way this is possible is if the Referrer is /post and not / or /discover like it should be. Can we confirm/deny this if you inspect the POST /post requests? 🤔

See this code

if htmx.IsHTMX(r) {
  htmx.NewResponse().
  Location(RedirectRefererURL(r, s.config, "/")).
  Write(w)
} else {
  http.Redirect(w, r, RedirectRefererURL(r, s.config, "/"), http.StatusFound)
}

@prologic@twtxt.net Okay lemme see

Indeed /post is referrer…

GET /post HTTP/2
Host: we.loveprivacy.club
[…]
HX-Request: true
HX-Target: content
HX-Current-URL: https://we.loveprivacy.club/conv/vcpt7gq
Referer: https://we.loveprivacy.club/post

@eldersnake@we.loveprivacy.club I mean on the POST /post request itself. That’s the Referer that’s looked up and used as the redirect.

Yeah sorry just realised, but just checked again and the referrer is the same (/post) on either the POST or the GET 🤔

For example, this is what you should see:

The POST /post XHR (that is being run by htmx) should never, ever be Referer: .../post 🤦‍♂️