Has it been shortened after the encoded url parameter is deciphering done?
3 views
Skip to first unread message
goon
Dec 7, 2009, 7:49:32 AM12/7/09
to Cli.gs Interested
I am API user.There is one question.
http://cli.gs/api/v1/cligs/create?url=$key
I am setting to $key as "http:\/\/example.com\/%e6%97%a5%e6%9c%ac%e8%aa
%9e".
http://cli.gs/***** is responsed as a result.
it's okay.
However, after decoding doing %e6%97%a5%e6%9c%ac%e8%aa%9e, are not you
shortening URL?
The garble is generated by a part of browser when forwarded to URL
that does the decode.
Isn't there something good solution?
http://cli.gs/api/v1/cligs/create?url=$key
I am setting to $key as "http:\/\/example.com\/%e6%97%a5%e6%9c%ac%e8%aa
%9e".
http://cli.gs/***** is responsed as a result.
it's okay.
However, after decoding doing %e6%97%a5%e6%9c%ac%e8%aa%9e, are not you
shortening URL?
The garble is generated by a part of browser when forwarded to URL
that does the decode.
Isn't there something good solution?
Reply all
Reply to author
Forward
0 new messages