some remote users fail to fetch due to content-type mismatch?

https://epic.dansmonorage.blue/users/fdc

@bob@epicyon.libreserver.org

@loppear@micro.mnino.us

when fetching these, I get Validate content type of AP response: Content type is not application/activity+json or application/ld+json, but curl tells me that the content-type is indeed application/activity+json

add some debug prints, figure out what's going on, and see if it's a problem on our end or on epicyon's end

thanks to arubes.slothrun on Discord for reporting the issue

added bugbackend low priority labels

probably not our bug ☹

curl -v -H 'accept: application/activity+json, application/ld+json; profile="https://www.w3.org/ns/activitystreams"' https://epic.dansmonorage.blue/users/fdc (the same accept header that we use in our requests) shows a content-type: application/ld+json, which is not valid (lacks the profile); if we do not send an accept (or we only send the first half), we get content-type: application/activity+json

same for the others. I'll suggest reporting the problem to Epicyon

closed