Unverified50% confidenceFactExact time
The behavior of URL fragments not being sent to the server is established by the RFC 3986 specification, originally designed for in-page navigation.
1
Sources
50%
Confidence
Long-term
Relevance
10/12/2026
First Seen
Sources
Related Entities
Related Claims
Unverified资源URL采用类似greeting://{name}的自定义协议格式，借鉴了URI模板（RFC 6570）规范74% similarUnverifiedThe URL fragment (the part after the # symbol) is never sent to the server; the server and intermediate proxies can only see the path portion.71% 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.67% 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.66% similarUnverifiedThe publishing page allows users to customize the application's URL, but the platform's domain suffix is permanently retained and cannot be removed.63% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1003630API
curl https://kongchang.com/api/v1/knowledge/claims/1003630MCP
get_claim(id=1003630)