Peter Bhat Harkins on Nostr: Real irritating puzzle: is there no way with Rack to access the raw client headers? ...
Real irritating puzzle: is there no way with Rack to access the raw client headers? I'm debugging a problem and want to see the actual header sent. I care if the client sent "user-agent" vs "user_agent" vs "User-Agent", but they all seem to be smashed to HTTP_USER_AGENT. Dude, where's my data?
Published at
2025-12-08 17:21:01 UTCEvent JSON
{
"id": "8985cf97c8702cafa7025c28b8cddc315f3d515c0ea7ad5df7cf59c4d81ebb3d",
"pubkey": "54c5cf3f3f91ed490315d610d6941e036af30ac450d8b723fbd40d1b37d8e1d9",
"created_at": 1765214461,
"kind": 1,
"tags": [
[
"proxy",
"https://ruby.social/users/pushcx/statuses/115685094937122214",
"activitypub"
],
[
"client",
"Mostr",
"31990:6be38f8c63df7dbf84db7ec4a6e6fbbd8d19dca3b980efad18585c46f04b26f9:mostr",
"wss://relay.ditto.pub/"
]
],
"content": "Real irritating puzzle: is there no way with Rack to access the raw client headers? I'm debugging a problem and want to see the actual header sent. I care if the client sent \"user-agent\" vs \"user_agent\" vs \"User-Agent\", but they all seem to be smashed to HTTP_USER_AGENT. Dude, where's my data?",
"sig": "2b9c97165eea60b9431f39b366afa778c9c0b99e4fc186b366580ec869ad9f432a1d4fb5230d08a6f8da9a75ba856ff060d30d24ae987bca2e8ddbca31f7f30e"
}
