Custom Uri format throws Malformed exception
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
Research direction
Start by locating the Ring middleware handling the :absolute-redirects option and reproduce the example with the custom blah:// URI. Trace why the redirect is treated as a malformed URL; done means custom URI schemes no longer trigger the reported MalformedURLException while absolute redirects continue to work.
Written by the indexing model from the issue text.
Description
If using ring defaults with:
:absolute-redirects - Any redirects to relative URLs will be turned into redirects to absolute URLs, to better conform to the HTTP spec.
set to true,
Returning something like this:
{:status 302
:headers {"Location" (format "blah://blah?abc=%s" abc)}
:body ""}
Will throw -> java.net.MalformedURLException: unknown protocol: blah
Copied from https://github.com/ring-clojure/ring/issues/306#issuecomment-329920396
- Dominant language
- Clojure
- Stars
- 27
- Forks
- 13
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from ring-clojure/ring-headers
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
ring-clojure/ring-headers#5 · 9 comments ·
All issues in ring-clojure/ring-headers
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
.Needs Triage .Team/UXWest Priority:P3 Type:New Feature
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
-
needs triage
Difficulty 1/5 Under an hour Newbie friendliness 90/100