How to parse a utf-8 url?

[Thijs Koerselman]

Hi,

I'm trying to parse a utf-8 url, but the url.parse function doesn't
seem to like spaces.

var url = require("url");
var file_url = "http://myhost.nl:9090/some/path/myweirdfile æfqúsß.mp3";
console.log("parsed:" , url.parse(file_url));

This gives the following output:

parse: { protocol: 'http:',
slashes: true,
host: 'myhost.nl:9090',
port: '9090',
hostname: 'myhost.nl',
href: 'http://myhost.nl:9090/some/path/myweirdfile',
pathname: '/some/path/myweirdfile',
path: '/some/path/myweirdfile'
}

Where exactly do I need to tackle this and how?

Thijs

[Matt]

Spaces are encoded as a + in URLs.

Thijs

--
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 nod...@googlegroups.com
To unsubscribe from this group, send email to
nodejs+un...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

[Felipe Gasper]

puny code?

>--
>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 nod...@googlegroups.com
>To unsubscribe from this group, send email to
>nodejs+un...@googlegroups.com
>For more options, visit this group at
>http://groups.google.com/group/nodejs?hl=en?hl=en

--
Sent from my Android phone with K-9 Mail. Please excuse my brevity.

[Isaac Schlueter]

The URL parser doesn't parse spaces.

It would be good to maybe discuss this, as it's a common complaint.

Let's discuss it in this issue: https://github.com/joyent/node/issues/3270

[Thijs Koerselman]

Thanks Isaac. That discussion makes it clear. I'm all for. I will just
escape the spaces myself for now but it would be great if this is
handled in url.parse. I would like to be able to retrieve the filename
from the parsed data as it is, with spaces and all.

Cheers,
Thijs

[Isaac Schlueter]

Thijs,

Well, if we do this, you'll get it with the spaces converted to %20.
It'll be up to you to call decodeURIComponent on it.

Spaces are actually not allowed in URLs, after all.

[Matt]

Another argument for a parsed_path value. Though again we have to realise that comes with an overhead, which is worth considering.

[Thijs Koerselman]

Hi Isaac,

> Well, if we do this, you'll get it with the spaces converted to %20.
> It'll be up to you to call decodeURIComponent on it.
>
> Spaces are actually not allowed in URLs, after all.
>

Yep that's all fine with me. At least I don't have to replace the " "
with "%20" manually before using the url.

[Isaac Schlueter]

Landed on 9fc7283a403bb0dec096b76991226cba8e7b73c2 in master.