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

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