url decode parameters
|
October 26, 2005, 04:40 PM
|
|
Hi,
I'm uploading photos+tags pretty well via /services/upload/.
However, some of my tags have spaces and what not in them, so I url encode everything on the way up.
And it doesn't look like they ever get url decoded as I'm seeing tags like "foo%2Es" and "a+space" instead of "foo's" and "a space", respectively.
Thanks.
|
| |
|
Team 23
October 28, 2005, 11:07 AM
|
|
Hey,
This behaviour should have been changed now. A note though: This bug has only been relevant when posting to the REST interface while still placing the parameters in the url query string. And my fantastic question to this: Why would you do this?
/Stc
|
| |
|
|
October 28, 2005, 03:12 PM
|
|
...Hm...good question.
I'm not using the URL parameters, but a multipart/form-data POST with the tags/photo/etc.
So, now that I think about it, you're right, I shouldn't have to url encode anything.
However, the behavior I noticed early on was that if I posted a photo with a tag like "a space" it ended up with 2 tags, 1 "a" and 1 "space".
My hack was to url encode, so then a "+" gets put in there.
But you're right, that is not the right way to solve it.
So...can 23 tags just not have spaces?
I suppose I could just replace all " " with "_".
|
| |
|
|
Team 23
October 28, 2005, 03:22 PM
|
|
Have you checked your application now? My guess is that you'll see that the problem's solved (as we're decoding the input from the url query and combining it into the post data).
/Stc
|
| |
|
