Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Switch to a more liberal URI parser implementation
See original GitHub issueWireMock uses Java’s URI class which prohibits some characters that most browsers and web servers are OK with.
Suggest fixing this by implementing a URL model that matches real-world parsing behaviour more closely.
I haven’t been able to find anything open source that does this job well, but if such a library exists this would probably be preferable to rolling one.
Issue Analytics
- State:
- Created 6 years ago
- Comments:10
Top Results From Across the Web
Switch to a more liberal URI parser implementation · Issue #713 ...
Suggest fixing this by implementing a URL model that matches real-world parsing behaviour more closely. I haven't been able to find anything open...
Read more >Easy URL Parsing With Isomorphic JavaScript - SitePoint
Most web applications require URL parsing whether it's to extract the domain name, implement a REST API or find an image path.
Read more >787361 - URI parser/Omnibox accept obscure and misleading ...
RFC 952 specifies that at least the first character of a hostname has to be a letter, but in RFC 1123 section 2.1...
Read more >Security Implications of URL Parsing Differentials
In this blog post, we detail how differential URL parsing bugs can ... and can require the progressive implementation of precise heuristics ...
Read more >Equivocal URLs: Understanding the Fragmented Space of ...
among parser implementations, leading to ambiguity that can be abused ... motivating a systemic adoption of a more unified URL parsing standard.
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 Free
Top 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
Hi! I’m problem with characters - ‘{’ and ‘}’ Example URL: http://<DOMAIN>/path?params={“param1”:“param2”}&ver=123&type=TYPE where character ‘"’ - is %22 Problem: https://tools.ietf.org/html/rfc1738 - page3 - These characters are “{”, “}”, “|”, "", “^”, “~”, “[”, “]”, and “`”.
When are you planning to implement this functionality?
@ravikumarser that sounds like a wholly different problem to me. Please can you open a new issue with a full, failing test case that replicates the problem?