On Thu, Apr 26, 2012 at 11:23 AM, Isaac Schlueter <[email protected]> wrote:
> It wouldn't be out of the question to add a decoded version of the
> path. It'd have to be a new member, though, and perform adequately
> (maybe a flag to enable it or something.)
>
Of course. I wasn't really asking for it to be changed - hopefully any
libraries are already coping with this already.
> But I don't think it's really that pressing of an issue.
No the question was just whether there was logic behind it - I wanted to
make sure I wasn't wildly off base :)
As long as express/connect don't interpret %3F as the start of the
querystring like Sinatra does then we're all good. I'm fairly sure they
won't given the following is parsed right:
> url.parse("http://host/something%3F%20here?a=b";, true);
{ protocol: 'http:',
slashes: true,
host: 'host',
hostname: 'host',
href: 'http://host/something%3F%20here?a=b',
search: '?a=b',
query: { a: 'b' },
pathname: '/something%3F%20here',
path: '/something%3F%20here?a=b' }
Matt.
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en
