Hi guys,
I have come across som a bug or unintuitive behaviour in uri-common. The
port parameter is reset on update-uri. uri-generic works like expected:
csi -R uri-generic
#;1 (update-uri (make-uri port: 100) scheme: 'http)
#(URI scheme=http authority=#(URIAuth host=#f port=100) path=()
On Tue, May 13, 2014 at 01:38:16PM +0200, Kristian Lein-Mathisen wrote:
Hi guys,
I have come across som a bug or unintuitive behaviour in uri-common. The
port parameter is reset on update-uri. uri-generic works like expected:
csi -R uri-generic
#;1 (update-uri (make-uri port: 100) scheme:
Hmmm ... The scheme is changed, like you say, but the port is too, from 100
to #f, which is what I find surprising.
I cannot seem to find a way to update the uri without loosing the port.
What am doing wrong here?
K.
On May 13, 2014 1:48 PM, Peter Bex peter@xs4all.nl wrote:
On Tue, May 13,
On Tue, May 13, 2014 at 11:25:23PM +0200, Kristian Lein-Mathisen wrote:
Hmmm ... The scheme is changed, like you say, but the port is too, from 100
to #f, which is what I find surprising.
I cannot seem to find a way to update the uri without loosing the port.
What am doing wrong here?
Try
A, of course, now I understand what you were trying to tell me previously.
That makes sense. Thanks for clarifying, Peter.
In my particular use-case, I am changing to a custom scheme and this port
clear on scheme change feature made me scratch my head for a while (but
that happens quite often, so
On Tue, May 13, 2014 at 11:37:53PM +0200, Kristian Lein-Mathisen wrote:
A, of course, now I understand what you were trying to tell me previously.
That makes sense. Thanks for clarifying, Peter.
Glad my ramblings were helpful!
In my particular use-case, I am changing to a custom scheme and
Peter Bex scripsit:
If anyone on this mailinglist has strong opinions either way, please let
yourselves be heard: now's the time to speak up.
I think the existing behavior is correct, because scheme and port are
tied together.
--
John Cowan http://www.ccil.org/~cowan
