On Sat, Jun 07, 2014 at 09:01:01PM -0400, John Cowan wrote:
Peter Bex scripsit:
c) The port should not be reset, but the uri should be printed without
port if it's the default for this scheme.
+1 for (c).
hm, but if you really want to print http://foo:80/blabla, how
should that
Peter Bex scripsit:
hm, but if you really want to print http://foo:80/blabla, how
should that work?
Why would you? It means exactly the same thing as http://foo/blabla
and it's longer.
--
John Cowan http://www.ccil.org/~cowanco...@ccil.org
Go, and never darken my towels
Hi,
So here's a new poll:
a) The current behaviour of resetting port to #f if it's the default port
for this scheme is ok.
b) The port should not be reset, and the uri should be printed with an
explicit port, even if it's the default for this scheme.
c) The port should not be reset,
On 2014-06-08 11:14, Peter Bex wrote:
On Sat, Jun 07, 2014 at 09:01:01PM -0400, John Cowan wrote:
Peter Bex scripsit:
c) The port should not be reset, but the uri should be printed without
port if it's the default for this scheme.
+1 for (c).
hm, but if you really want to
