Re: NSURL fileURLWithPath doesn't produce a valid URL
Re: NSURL fileURLWithPath doesn't produce a valid URL
- Subject: Re: NSURL fileURLWithPath doesn't produce a valid URL
- From: Richard Frith-Macdonald <email@hidden>
- Date: Fri, 31 Jul 2009 09:02:10 +0100
On 31 Jul 2009, at 08:34, Alexander Bokovikov wrote:
On 31.07.2009, at 11:51, Dave Keck wrote:
Check out CFURLCreateStringByAddingPercentEscapes(), and note that
CFURL is toll-free bridged with NSURL.
Just have tried it. No difference. I've used:
surl = CFURLCreateStringByAddingPercentEscapes(kCFAllocatorDefault,
spath,
NULL,
NULL,
kCFStringEncodingUTF8);
where spath was the source string with "+" signs. I've set NULL's,
as it was described (at least as I've understood what was written)
to escape any possible characters. Is "+" sign not considered by
Apple, as a character, which requires escaping?
In my opinion, all codes since 0x20 to 0x2F require escaping. Am I
incorrect?
The '+' sign doesn't require escaping to create a valid URL
eg. 'file:///tmp/x+y' is a perfectly valid URL.
Why do you think that's not a valid URL? If you look at RFC1738 you
will see it explicitly says that a '+' is allowed.
I suspect what you are actually looking for is a mechanism to encode a
string for use as a field name or field value in a form encoded as the
query string of a URL. If thats the case, you need to encode the '+'
'=' and '&' characters yourself.
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden