EDIT: Okay, convo works properly now at least
126.0.1 🤣
126.0.1 🤣
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 🐛
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 🐛
* aa2f3ae9 - (HEAD -> main, origin/main) Workaround for this invalid Referer BS (6 seconds ago) <James Mills>
* aa2f3ae9 - (HEAD -> main, origin/main) Workaround for this invalid Referer BS (6 seconds ago) <James Mills>
>server {
listen 80;
server_name we.loveprivacy.club;
location / {
return 301 https://$host$request_uri;
#proxy_pass 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;
}
}
>
Referer is /post then consider that total bullshit, and ignore? 🤔
Referer is /post then consider that total bullshit, and ignore? 🤔
Referer header incorrectly?! 🤔
Referer header incorrectly?! 🤔
POST /post followed by a GET <from> where ever I was coming from. Hmmm 🧐 
This is nuts 🌰
POST /post followed by a GET <from> where ever I was coming from. Hmmm 🧐 This is nuts 🌰
You can see here, at least, htmx knows what the current URL is:
HX-Current-URL: https://we.loveprivacy.club/conv/vcpt7gq
Referer: https://we.loveprivacy.club/post
But the freak'n browser is setting the wrong value for
Referer. There is simply no way to be on the /post endpoint normally anyway.
You can see here, at least, htmx knows what the current URL is:
HX-Current-URL: https://we.loveprivacy.club/conv/vcpt7gq
Referer: https://we.loveprivacy.club/post
But the freak'n browser is setting the wrong value for
Referer. There is simply no way to be on the /post endpoint normally anyway.
kept it in zone 2 pretty well
#running #treadmill
kept it in zone 2 pretty well
#running #treadmill
kept it in zone 2 pretty well
#running #treadmill
POST /post XHR (_that is being run by htmx_) should never, ever be Referer: .../post 🤦♂️
POST /post XHR (_that is being run by htmx_) should never, ever be Referer: .../post 🤦♂️
/post) on either the POST or the GET 🤔
POST /post request itself. That's the Referer that's looked up and used as the redirect.
POST /post request itself. That's the Referer that's looked up and used as the redirect.
>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
>
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
g
if htmx.IsHTMX(r) {
htmx.NewResponse().
Location(RedirectRefererURL(r, s.config, "/")).
Write(w)
} else {
http.Redirect(w, r, RedirectRefererURL(r, s.config, "/"), http.StatusFound)
}
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
g
\t\tif htmx.IsHTMX(r) {
\t\t\thtmx.NewResponse().
\t\t\t\tLocation(RedirectRefererURL(r, s.config, "/")).
\t\t\t\tWrite(w)
\t\t} else {
\t\t\thttp.Redirect(w, r, RedirectRefererURL(r, s.config, "/"), http.StatusFound)
\t\t}
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
g
if htmx.IsHTMX(r) {
htmx.NewResponse().
Location(RedirectRefererURL(r, s.config, "/")).
Write(w)
} else {
http.Redirect(w, r, RedirectRefererURL(r, s.config, "/"), http.StatusFound)
}
GET /, You are right that a POST /post does an internal XHR redirect to whatever view you're on to refresh it.
GET /, You are right that a POST /post does an internal XHR redirect to whatever view you're on to refresh it.
>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
GET /post -- There is no handler/route for that, that *will* indeed 404, really strange you're still seeing this? And what's this login issue?
GET /post -- There is no handler/route for that, that *will* indeed 404, really strange you're still seeing this? And what's this login issue?
DEBU[0163] no subscriptions found for http://10.0.0.164:8000/user/admin/twtxt.txt
[yarnd] 2024/06/19 23:13:23 (10.0.0.164:64888) "POST /post HTTP/1.1" 200 0 8.323709ms
DEBU[0163] reloading templates in debug mode...
[yarnd] 2024/06/19 23:13:23 (10.0.0.164:64888) "GET / HTTP/1.1" 200 18120 87.933208ms
for every post there should be a
POST /post ... followed pretty quickly by a GET /
DEBU[0163] no subscriptions found for http://10.0.0.164:8000/user/admin/twtxt.txt
[yarnd] 2024/06/19 23:13:23 (10.0.0.164:64888) "POST /post HTTP/1.1" 200 0 8.323709ms
DEBU[0163] reloading templates in debug mode...
[yarnd] 2024/06/19 23:13:23 (10.0.0.164:64888) "GET / HTTP/1.1" 200 18120 87.933208ms
for every post there should be a
POST /post ... followed pretty quickly by a GET /
go v1.22.2 here, but I'll upgrade now just to be sure...
go v1.22.2 here, but I'll upgrade now just to be sure...
go v1.22.2 here, but I'll upgrade now just to be sure...
* 8eef4d5d - (HEAD -> main, origin/main) Add DB restore capability and tools/backu-_db.sh script (19 seconds ago) <James Mills>
Oh well 😅 It works wonderfully!
In the event of a database corruption or loss:
$ URL=http://10.0.0.164:8000 ./tools/backup_db.sh > db.json
mv db.json data/db.restore.json
yarnd ...
* 8eef4d5d - (HEAD -> main, origin/main) Add DB restore capability and tools/backu-_db.sh script (19 seconds ago) <James Mills>
Oh well 😅 It works wonderfully!
In the event of a database corruption or loss:
$ URL=http://10.0.0.164:8000 ./tools/backup_db.sh > db.json
mv db.json data/db.restore.json
yarnd ...
That's why I was wondering if using Go 1.22.4 could be an issue. I don't know how exactly. Only way to test is to rebuild it with an older version I guess, which is why I did the make clean in the first place. Old habits die hard lol.