Unverified50% confidenceFactExact time
The Authorization header stripping behavior in HTTP redirects is directly related to the security recommendations in RFC 7235 and subsequent HTTP specifications.
1
Sources
50%
Confidence
Long-term
Relevance
10/19/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedIn the HTTP protocol specification RFC 7231, the GET method is defined as a safe method that should not produce side effects on server resources.71% similarUnverifiedRFC 9728 (Protected Resource Metadata) lets resource servers publish the information needed for the trust chain through a standardized endpoint; RFC 8414 (Authorization Server Metadata) is used to expose the authorization server's endpoints, supported grant types, and signing algorithms; RFC 8707 (Resource Indicators) specifies that clients explicitly declare the target resource in authorization requests and token requests, enabling the authorization server to issue audience-bound tokens.68% similarUnverifiedRFC 9116 was officially published by the IETF in 2022 and specifies the standard format for security.txt files, including fields such as Contact, Expires, Encryption, and Policy.65% similarUnverifiedCustom Connectors only support REST APIs exposed via HTTPS.65% similarUnverifiedModern browsers display a 'Not Secure' warning for HTTP websites, and certain features such as accessing geolocation and camera permissions are only available to HTTPS websites.64% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1068240API
curl https://kongchang.com/api/v1/knowledge/claims/1068240MCP
get_claim(id=1068240)