Σε απευθείας σύνδεση Url κωδικοποιητή

Salvete! I have discovered that a certain way of url encoding breaks the link. For the record %2f represents the forward slash character: /

Now, consider this:Original Link: http://dottech.org/95285/this-is-the-pacific-barreleye-a-fish-with-a-transparent-head-amazing-photo-of-the-day

javascript (encodeURIComponent) urlencoded link: http://dottech.org%2f95285%2fthis-is-the-pacific-barreleye-a-fish-with-a-transparent-head-amazing-photo-of-the-day

Now, if you paste the encoded link into your browser's address bar, it is broken (Firefox, Chrome, IE).

However, if you don't url-encode the first forward slash, it works perfectly:'http://dottech.org/95285%2fthis-is-the-pacific-barreleye-a-fish-with-a-transparent-head-amazing-photo-of-the-day

Why?

This is my url .my problem is address not appending to urlpath . plz help me

var address:stringaddress = "American Tourister, Abids Road, Bogulkunta, Hyderabad, Andhra Pradesh, India"let urlpath = NSString(format: "http://maps.googleapis.com/maps/api/geocode/json?address="+"\(address)")

I have an nginx reverse-proxy which needs to pass on the query string it receives. However this query string it receives is not well formatted and can contain JSON that is not URL encoded i.e. it contains curly brackets i.e. {}, commas, colons and double quotes! Unfortunately, I have no control over this and this causes the downstream server to barf when parsing the string.

Is there a way to correctly URL encode this string before proxying it?

I can replace the curly brackets as I know there will only be one instance of each using the config:

if ($args ~* '(.*){(.*)}(.*)') {    set $args $1%7B$2%7D$3;    rewrite (.*)$ $1;}proxy_pass http://127.0.0.1:8080;

However, I don't know in advance how many fields the JSON will have so it's difficult to use the same logic as above for the rest of the object.

I should also mention that I don't think this is related to nginx url-decoding parameters as I am not using a URI in the proxy_pass.

Thanks!

UPDATE: For the time being, the JSON object seems to be sending the same properties so this is what I've used as a workaround. It's pretty hideous and will break if the number of properties changes but does the job for now.

if ($args ~* '(.*){"(.*)":"(.*)","(.*)":"(.*)","(.*)":"(.*)","(.*)":"(.*)","(?<group10>.*)":"(?<group11>.*)"}(?<group12>.*)') {    set $args $1%7B%22$2%22%3A%22$3%22%2C%22$4%22%3A%22$5%22%2C%22$6%22%3A%22$7%22%2C%22$8%22%3A%22$9%22%2C%22${group10}%22%3A%22${group11}%22%7D${group12};    rewrite (.*)$ $1;}proxy_pass http://127.0.0.1:8080;

Note that since this returns more than 9 regex groups, I had to name groups 10, 11 and 12 otherwise they get interpreted as $1 + the digit 0, 1 or 2.

Is there a more robust way of doing this?

I have a default value that contains a '%' which I also insert in to the help doc of my argument. E.g.:

default = "5% foo"animrender_group.add_argument(    "--foo",    default=default,    help="Foo amount. Default: %s" % default,)args = parser.parse_args()

Argparse errors on parse_args()

[snip]    args = parser.parse_args()[snip]"../python2.5/site-packages/argparse.py", line 622, in _expand_help    return self._get_help_string(action) % paramsValueError: unsupported format character 'O' (0x4f) at index 83

I have been trying to access a URL with a / character in it from powershell, using the following command (it's a query to a gitlab server to retrieve a project called "foo/bar"):

Invoke-WebRequest https://server.com/api/v3/projects/foo%2Fbar -Verbose

Now, the odd thing is that using the PowerShell ISE or Visual Studio, the request is OK. When using PowerShell itself, the URL is automatically un-escaped and the request fails. E.g.

In ISE/VS:

$> Invoke-WebRequest https://server.com/api/v3/projects/foo%2Fbar -VerboseVERBOSE: GET https://server.com/api/v3/projects/foo%2Fbar with 0-byte payloadVERBOSE: received 19903-byte response of content type application/jsonStatusCode        : 200StatusDescription : OKContent           : .... data ....

In Powershell:

$> Invoke-WebRequest https://server.com/api/v3/projects/foo%2Fbar -VerboseVERBOSE: GET https://server.com/api/v3/projects/foo/bar with 0-byte payloadInvoke-WebRequest : {"error":"404 Not Found"}At line:1 char:1+ Invoke-WebRequest 'https://server.com/api/v3/projects/foo%2Fbar ...+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~    + CategoryInfo          : InvalidOperation: (System.Net.HttpWebRequest:HttpWebRequest) [Invoke-WebRequest], WebException    + FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeWebRequestCommand

I have tried adding single and double quotes around the URL, but nothing is helping.

What could be the reason for this behaviour, and how do I make PS not un-escape the URL string?

Environment: Windows 7, also tested on Server 2012R2 with same results.

$> $PSVersionTableName                           Value----                           -----PSVersion                      4.0WSManStackVersion              3.0SerializationVersion           1.1.0.1CLRVersion                     4.0.30319.42000BuildVersion                   6.3.9600.16406PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0}PSRemotingProtocolVersion      2.2