| Age | Commit message (Collapse) | Author |
|---|
|
When we check to see if the underlying path must be updated
to be present, we should know that uri-common is faking a
path of (/ "") when the path is empty.
The path normalization in uri-common could use some work though,
as it never really touches the underlying uri-generic object.
On the other hand, this is sort of the promise that uri-common
tries to make - it never mangles the uri object unless you explicitly
update something yourself.
|
|
That path should also have a trailing slash just like when
requesting a regular URI. See #1781
|
|
|
|
|
|
(which is disallowed by RFC)
|
|
|
|
Keywords can't be (ab)used as identifier anymore, so we can't bind
expression: with let-syntax. Instead, simply use the plain symbol.
|
|
|
|
Thanks to Norman Gray for pointing out that the response was missing
from the condition object.
|
|
|
