Which is why I suggested using it... It is "guaranteed" to not be part of the URL and therefore serves as a good field delim.
On Aug 28, 2013, at 12:02 PM, Daniel Lescohier <daniel.lescoh...@cbsi.com> wrote: > This value is in the format of a URL; | is in the list of 'unsafe' chars for > URLs. Perhaps use semi-colon instead? > > sock://var/run/server.sock;/foo/bar > > > > On Wed, Aug 28, 2013 at 8:00 AM, Jim Jagielski <j...@jagunet.com> wrote: > > On Aug 27, 2013, at 7:09 PM, Daniel Ruggeri <drugg...@primary.net> wrote: > > > On 8/23/2013 2:50 PM, Jim Jagielski wrote: > >> I've also looked at (and am hoping it works out) > >> > >> sock://var/run/server.sock|http://localhost/foo/bar > >> > >> The reason I like using '|' is it's quite Perlish :) > >> The other advantage is that it keep both "sides" completely > >> separate and self-contained. > > > > I like this one better... it's definitely the "cleanest" representation. > > I'm assuming that the post-pipe stuff gets parsed as usual and then > > 'localhost' gets sent as the Host header (unless ProxyPreserveHost is set)? > > Yeah... in fact, in my current local branch, this is the format > I'm using. It makes things *much* cleaner. >
