[racket] Preventing get-impure-port from url-encoding the query

For what it's worth, the url in the query section is used for redirection
after shibboleth authentication at a large institution. I don't anticipate
that changing. I do think, however, that what strikes me as an increasing
preponderance of 'creative' url interpretation in the age of SAAS may make
a case for greater control over the path/query/fragment portion of the url,
whether or not that falls under the official heading of net/'url's.


On Thu, Jul 11, 2013 at 11:39 AM, Sam Tobin-Hochstadt <samth at ccs.neu.edu>wrote:

> First, I think in this particular case the RFCs agree with Evan here.
> In particular, see section 3.4 of RFC 3896:
> http://tools.ietf.org/html/rfc3986#section-3.4 which defines query
> strings as containing a sequence of either 'pchar', "/" or "?", where
> 'pchar' includes ":", ascii alphanumeric characters, "." and
> 'sub-delims', which includes "=".
>
> Second, you (and I) may not like the specification style demonstrated
> in the URL spec, but that's the direction that a lot of web standards
> are going.  You can see it in the HTML spec, too:
> http://www.w3.org/TR/html5/ . These are the specifications that
> implementors of web browsers and web servers are paying attention to
> and contributing to, and thus they're the ones we need to pay
> attention to.
>
> Sam
>
> On Thu, Jul 11, 2013 at 2:19 PM, Jay McCarthy <jay.mccarthy at gmail.com>
> wrote:
> > This debate is bigger than you and me, but I don't see a spec here. I
> > see a weird pseudo-code parsing algorithm with no specification. In
> > any case, the net/url module implements the RFCs. If those aren't what
> > you want, then it needs to be changed or a new module needs to be
> > implemented. Given the big different between the RFCs and this new
> > "specification", I gather there won't be a lot of shared code.
> >
> > Jay
> >
> > On Thu, Jul 11, 2013 at 12:16 PM, Sam Tobin-Hochstadt <samth at ccs.neu.edu>
> wrote:
> >> I'm not sure which spec you're looking at from there, but the URL spec
> >> that I linked to is the most current work on precisely specifying
> >> URLs.
> >>
> >> On Thu, Jul 11, 2013 at 2:14 PM, Jay McCarthy <jay.mccarthy at gmail.com>
> wrote:
> >>> I'm looking at the spec: http://www.w3.org/Addressing/
> >>>
> >>> On Thu, Jul 11, 2013 at 11:59 AM, Sam Tobin-Hochstadt <
> samth at ccs.neu.edu> wrote:
> >>>> On Thu, Jul 11, 2013 at 1:46 PM, Jay McCarthy <jay.mccarthy at gmail.com>
> wrote:
> >>>>> On Wed, Jul 10, 2013 at 5:27 PM, Evan Donahue <emdonahu at gmail.com>
> wrote:
> >>>>>> Hello, I am trying to use the racket networking libraries for a
> basic set of
> >>>>>> get and post requests. I need to send a url of the form:
> >>>>>>
> >>>>>> http://foo.com/?url=http://bar.com?baz=1000 (NOT form encoded)
> >>>>>
> >>>>> As far as I can tell from URL specs, this is not a URL.
> >>>>
> >>>> I don't think that's correct. In particular, see
> >>>> http://url.spec.whatwg.org/#query-state and step 3 there, as well as
> >>>> the definition on URL code point here:
> >>>> http://url.spec.whatwg.org/#url-code-points which includes all of the
> >>>> characters in Evan's query.
> >>>>
> >>>> Sam
> >>>
> >>>
> >>>
> >>> --
> >>> Jay McCarthy <jay at cs.byu.edu>
> >>> Assistant Professor / Brigham Young University
> >>> http://faculty.cs.byu.edu/~jay
> >>>
> >>> "The glory of God is Intelligence" - D&C 93
> >
> >
> >
> > --
> > Jay McCarthy <jay at cs.byu.edu>
> > Assistant Professor / Brigham Young University
> > http://faculty.cs.byu.edu/~jay
> >
> > "The glory of God is Intelligence" - D&C 93
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.racket-lang.org/users/archive/attachments/20130711/48fc0ae1/attachment.html>