@julian @liaizon @rimu I'm not getting any error 500. Response is coming back fine.
Conversation
Notices
-
Embed this notice
Rich Felker (dalias@hachyderm.io)'s status on Wednesday, 25-Feb-2026 10:34:43 JST
Rich Felker
-
Embed this notice
Julian Fietkau (julian@fietkau.social)'s status on Wednesday, 25-Feb-2026 10:34:45 JST
Julian Fietkau
@dalias @liaizon ... or maybe not? I'm actually seeing the same behavior on piefed.social. Hey @rimu, what is the content negotiation doing on this route? Shouldn't this be going through? I hope I'm not so tired that I've missed a typo or something?
curl -H "Accept: application/activity+json" -v https://piefed.social/quote_boost_auth?stamp=https%3A%2F%2Fexample.com;https%3A%2F%2Fexample.com
-
Embed this notice
Julian Fietkau (julian@fietkau.social)'s status on Wednesday, 25-Feb-2026 10:34:46 JST
Julian Fietkau
@dalias @liaizon Wait, I think it's the server config at piefed.zip after all. If I try to request https://piefed.zip/quote_boost_auth?stamp=https%3A%2F%2Fpiefed.zip%2Fc%2Fprivacy%2Fp%2F1136724%2Fdiscord-cuts-ties-with-peter-thiel-backed-verification-software-after-its-code-was-found-t;https%3A%2F%2Fsocial.wake.st%2Fusers%2Fliaizon%2Fstatuses%2F116128410011052563 as application/activity+json via curl, I get an HTTP error 500. I can't think of a good reason why, but there must be something goofy going on there. Do we know their server admin @liaizon, would they want a ping about this?
-
Embed this notice
Julian Fietkau (julian@fietkau.social)'s status on Wednesday, 25-Feb-2026 10:34:47 JST
Julian Fietkau
@dalias @liaizon Okay, the length of the URI is probably not the reason. This authorization at https://piefed.zip/quote_boost_auth?stamp=https%3A%2F%2Fpiefed.zip%2Fc%2Fprivacy%2Fp%2F1131286%2Fwe-say-no-to-big-tech-mass-snooping-on-our-messages;https%3A%2F%2Ffietkau.social%2Fusers%2Fjulian%2Fstatuses%2F116128620152439918 is only 227 characters.
-
Embed this notice