Incorrect parsing of answer URL as question
See original GitHub issueBhargav reported this post in this chat message:
!!/report https://stackoverflow.com/questions/20038353/smooth-animation-when-tab-switches/48046679#48046679
The link was somehow parsed as a question link, resulting in this URL in the report (MS):
https://stackoverflow.com/questions/20038353
Issue Analytics
- State:
- Created 6 years ago
- Reactions:2
- Comments:8 (5 by maintainers)
Top Results From Across the Web
incorrect URL parsing · Issue #2114 · nodejs/node - GitHub
Yes. The test in the linked issue has the same result in io.js. A possible solution would be to simply parse the string...
Read more >Parse URL returns incorrect response - Stack Overflow
I have an installation of the Parse Server powered by Bitnami. I have modified the server.js code, and inserted appropriate keys. ... However,...
Read more >duplicity: problem parsing WebDAV URLs in bash script
I always run into parsing problems of the juxtaposed "@" symbol which, together with the WebDAV URL, will be parsed into the variable...
Read more >URL Inspection Tool - Search Console Help - Google Support
The URL Inspection tool provides information about Google's indexed version of a specific page, and also allows you to test whether a URL...
Read more >Creating URL query strings in Python
Invalid characters for URLs; How Python's urllib handles invalid URL characters ... That's actually a question we can't answer, unless we're running the ......
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
I’m not sure if ChatExchange uses the
/message/<message_id>
endpoint, but it is known to insert some invisible characters in between long URLs. In the one which I reported:The
‌​
character has appeared exactly after the/
which might have lead to an incorrect parsing of the URL.This was one reason why I had troubling parsing the URL in one of my bots earlier.
FWIW, this occurred again … here https://chat.stackoverflow.com/transcript/message/40942991#40942991. I’m sure that the invisible character stuff is the reason to blame.