[bug] Some redirects 404 for AP, only work for browser users #835
Labels
No labels
approved, awaiting change
bug
configuration
documentation
duplicate
enhancement
extremely low priority
feature request
Fix it yourself
help wanted
invalid
mastodon_api
needs docs
needs tests
not a bug
planned
pleroma_api
privacy
question
static_fe
triage
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: AkkomaGang/akkoma#835
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?
Your setup
No response
Extra details
No response
Version
"2.7.2 (compatible; Akkoma 3.13.2)"
PostgreSQL version
No response
What were you trying to do?
Found by https://github.com/superseriousbusiness/gotosocial/issues/2643#issuecomment-2370906204 :
You really have to make the redirects work for AP requests as well, otherwise it can’t work when a user searches for a URL an Akkoma user sent them on their own instance.
What did you expect to happen?
No response
What actually happened?
No response
Logs
No response
Severity
No response
Have you searched for this issue?
i disagree with your analysis
we are not the authority on remote users - requesting the AP data for
https://infosec.place/users/AlXRUAEjZWsAzH4Zm4
, which is actuallyhttps://bird.makeup/users/evilsocket
should indeed return 404 - you've requested AP, we cannot return that AP authoritatively, the url is not foundBut when an Akkoma user copies the link to a third-instance user’s profile and sends that link to me, it DOES NOT WORK unless you add the redirection which you ALREADY HAVE for the browser.
Just make it so that the 302 is also returned for AP requests and things will become interoperable.