Part of URL after hash sign (#) is removed during the request
See original GitHub issueKtor Version
1.2.0-rc
Ktor Engine Used(client or server and name)
ktor-client-apache:1.2.0-rc
JVM Version, Operating System and Relevant Context
Oracle JDK 8, Open JDK 11
Feedback
When trying to open an URL with #
sign in URL the part after hash is completely removed
Example:
val response = client.call("https://google.com#test") {
method = HttpMethod.Get
}.response
Actual request is going to be made to https://google.com
page instead of https://google.com#test
.
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Why is the hash part of the URL not available on the server ...
Explanation: Basically the hash component of the page URL (the part following the # sign) is processed by the browser only - the...
Read more >read url hash (#) part in server side - MSDN - Microsoft
I excepted that Request.Url.Fragment returns "main" in this case, but it returns allways an empty string. I search a lot and in the...
Read more >URI fragment - Wikipedia
The fragment identifier introduced by a hash mark # is the optional last part of a URL for a document. It is typically...
Read more >Use pound sign or hash mark in click-through - Studio Help
In a URL, a hash mark, number sign, or pound sign ( # ) points a browser to a specific spot in a...
Read more >URL location hash being cleared when it isn't authentication ...
What's happening is that the application domain session cookie okta-oauth-redirect-params is set from a previous instance of the application ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Fragment part (everything after
#
) assumed to be client-side only, it never should be submitted to the server.Might be (post-processing via JS in my case). Thank you @Prototik for your explanation!