Unverified50% confidenceFactExact time
The URL fragment (the part after the # symbol) is never sent to the server; the server and intermediate proxies can only see the path portion.
1
Sources
50%
Confidence
Long-term
Relevance
10/12/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedThe behavior of URL fragments not being sent to the server is established by the RFC 3986 specification, originally designed for in-page navigation.71% similarUnverifiedWhen a URL path is shared by multiple requests, setting a breakpoint directly will cause it to be triggered before the pagination event; a target interface path filter should be written in the breakpoint condition.65% similarUnverifiedThe World Wide Web uses unidirectional links: clicking a link navigates to another page, but the target page has no knowledge of who linked to it.63% similarUnverifiedThe URL links provided by the model may themselves be products of hallucination, potentially generating plausible-looking but non-existent web addresses, so clicking to verify is indispensable.59% similarUnverifiedIn web requests, newline characters (%0A or literal \n) in URL paths or query parameters are legitimate encoded characters that the HTTP layer does not automatically filter.59% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1003629API
curl https://kongchang.com/api/v1/knowledge/claims/1003629MCP
get_claim(id=1003629)