[Bug] Malformed HTTP requests causing 404 errors #181
Labels
No labels
a11y
Bug
Bug fix
Critical Priority
Documentation
Feature
Feature request
Held for next release cycle
High Priority
Low Priority
Medium Priority
Minor change
Translation/Locale
WIP
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: AkkomaGang/akkoma-fe#181
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Steps to reproduce:
Observed behaviour:
Two 404 errors appear
Example on https://outerheaven.club/notice/AOSE9pm6Ykf152HiVM (which is a private post) where I get an error on https://outerheaven.club/api/v1/accounts/AOSE9pm6Ykf152HiVM?with_relationships=true and https://outerheaven.club/api/v1/accounts/null/statuses?with_muted=true&exclude_replies=1&limit=20
On public posts like https://outerheaven.club/notice/ANJpfDZZYs1P61EhNY the only error that appear is 1. on https://outerheaven.club/api/v1/accounts/ANJpfDZZYs1P61EhNY?with_relationships=true
The issue seems to only appear when going from viewing an user's profile to a post. Doing so on the timeline doesn't seem to result in 404s
users ANJpfDZZYs1P61EhNY and AOSE9pm6Ykf152HiVM indeed appear to not exist on your instance - it may be a deactivated account or similar
we'll have to decode the ID to do any meaningful debugging
can you run this on your db?
(obviously change the db name if you need)
Welp, they don't even exist in my DB
What was the conclusion 🤔?
It's still happening quite frequently when I open threads, but I don't really have more info than what I already provided. I'm assuming there's an issue with how these URLs are formed in the FE, but I may be wrong.
my hunch here is that it's something to do with suspended users (domain block etc etc)
there's another instance seeing some 404s when deleted users are around
ok i can't replicate anything on my side, i've requested an account on your instance to see if i can investigate it there, if that's ok
got it!
thanks for the account approval
it's trying to fetch the relationships of a note ID
wonder why
ahah
so get this - user profiles are told to switch users when the route parameter called
id
changes - only problem is that both/notice/:id
and/user/:id
... have an ID paramshould be fixed! if you update to develop pleroma-fe this should go away
This is very poggère, thanks for looking into it!
I don't recall seeing that issue since I've updated to the last stable, I'm closing it