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

I am trying to write a windows client application that calls a web site for data. To keep the install to a minimum I am trying only use dlls in the .NET Framework Client Profile. Trouble is that I need to UrlEncode some parameters, is there an easy way to do this without importing System.Web.dll which is not part of the Client Pofile?

I have an application which I've developed for a friend. It sends a POST request to the VB forum software and logs someone in (with out setting cookies or anything).

Once the user is logged in I create a variable that creates a path on their local machine.

c:\tempfolder\date\username

The problem is that some usernames are throwing "Illegal chars" exception. For example if my username was mas|fenix it would throw an exception..

Path.Combine( _        Environment.GetFolderPath(System.Environment.SpecialFolder.CommonApplicationData), _  DateTime.Now.ToString("ddMMyyhhmm") + "-" + form1.username)

I don't want to remove it from the string, but a folder with their username is created through FTP on a server. And this leads to my second question. If I am creating a folder on the server can I leave the "illegal chars" in? I only ask this because the server is Linux based, and I am not sure if Linux accepts it or not..

EDIT: It seems that URL encode is NOT what I want.. Here's what I want to do:

old username = mas|fenixnew username = mas%xxfenix

Where %xx is the ASCII value or any other value that would easily identify the character.

I have a PHP project where I need to send a hash character (#) within the path of a URL. (http://www.example.com/parameter#23/parameter#67/index.php) I thought that urlencode would allow that, converting the hash to %23

But now I see that even the urlencoded hash forces the browser to treat everything to the right as the URL fragment (or query).

Is there a way to pass a hash through, or do I need to do a character substitution prior to urlencode?

I am expecting

System.out.println(java.net.URLEncoder.encode("Hello World", "UTF-8"));

to output:

Hello%20World

(20 is ASCII Hex code for space)

However, what I get is:

Hello+World

Am I using the wrong method? What is the correct method I should be using?

I have generated a pre-signed S3 URL in java for HTTP PUT method.

A slightly modified version of the URL:

https://s3.amazonaws.com/somebucket/pre-signed-url-key-2?AWSAccessKeyId=BKIAIQ6H5Z7BG6KZ2ZUA&Expires=1425617244&Signature=GWcRM5ZIrAKnMJBsxyfm%2F9fyuBk%3D

I know that it is a valid pre-signed url since I can use it with curl to upload a file

curl -v --upload-file somefile.txt "https://s3.amazonaws.com/somebucket/pre-signed-url-key-2?AWSAccessKeyId=BKIAIQ6H5Z7BG6KZ2ZUA&Expires=1425617244&Signature=GWcRM5ZIrAKnMJBsxyfm%2F9fyuBk%3D"

When I try to upload a file to the same URL using the following Javascript:

function ajaxUsingPresignedUrlPut() {            $.ajax({                url: presignedURLPUT,                type: 'PUT',                data: 'blah blah blah',                success: function () {                    console.log('Uploaded data successfully.');                }            }).done(function (data) {                console.log("DONE : " + data);            }).fail(function (e, r) {                console.log("FAIL");            });        }

I get a 403 status and responseText

<?xml version="1.0" encoding="UTF-8"?><Error><Code>SignatureDoesNotMatch</Code><Message>The request signature we calculated does not match the signature you provided. Check your key and signing method.</Message><AWSAccessKeyId>BKIAIQ6H5Z7BG6KZ2ZUA</AWSAccessKeyId><StringToSign>PUTapplication/x-www-form-urlencoded; charset=UTF-81425617244/somebucket/pre-signed-url-key-2</StringToSign><SignatureProvided>GWcRM5ZIrAKnMJAsxyfm/9fyuAk=</SignatureProvided><StringToSignBytes>50 55 54 0a 0a 61 70 70 6c 69 63 61 74 69 6f 6e 2f 78 2d 77 77 77 2d 66 6f 72 6d 2d 75 72 6c 65 6e 63 6f 64 65 64 3b 20 63 68 61 72 73 65 74 3d 55 54 46 2d 38 0a 31 34 32 35 36 31 37 32 34 34 0a 2f 6e 6b 6f 6e 64 72 61 74 5f 62 75 63 6b 65 74 2f 70 72 65 2d 73 69 67 6e 65 64 2d 75 72 6c 2d 6b 65 79 2d 32</StringToSignBytes><RequestId>3C8298CAC404C6F5</RequestId><HostId>uCkzA//CdCLi4SINifkIe0WH6GOlCJBgFlN8ghx8NnULEe+QVslsdoUsJc4AUdA8</HostId></Error>

I have the following CORS policy configured on the S3 bucket:

<?xml version="1.0" encoding="UTF-8"?><CORSConfiguration xmlns="http://s3.amazonaws.com/doc/2006-03-01/">    <CORSRule>        <AllowedOrigin>*</AllowedOrigin>        <AllowedMethod>HEAD</AllowedMethod>        <AllowedMethod>GET</AllowedMethod>        <AllowedMethod>PUT</AllowedMethod>        <AllowedMethod>POST</AllowedMethod>        <AllowedMethod>DELETE</AllowedMethod>        <MaxAgeSeconds>3000</MaxAgeSeconds>        <ExposeHeader>ETag</ExposeHeader>        <ExposeHeader>Content-Length</ExposeHeader>        <ExposeHeader>Content-Type</ExposeHeader>        <ExposeHeader>Connection</ExposeHeader>        <ExposeHeader>Date</ExposeHeader>        <ExposeHeader>Server</ExposeHeader>        <ExposeHeader>x-amz-delete-marker</ExposeHeader>        <ExposeHeader>x-amz-id-2</ExposeHeader>        <ExposeHeader>x-amz-request-id</ExposeHeader>        <ExposeHeader>x-amz-version-id</ExposeHeader>        <AllowedHeader>*</AllowedHeader>    </CORSRule></CORSConfiguration>

And the same javascript code works for a pre-signed GET URL:https://s3.amazonaws.com/somebucket/pre-signed-url-key-2?AWSAccessKeyId=BKIBIQ6H5Z7LG6KZ2ZUB&Expires=1425616588&Signature=qMPpuzMwxonYPDQETdLafEQGqMU%3D

function ajaxUsingPresignedUrlGET() {            $.ajax({                url: presignedURLGET,                type: 'GET',                success: function () {                    console.log('Uploaded data successfully.');                }            }).done(function (data) {                console.log("DONE : " + data);            }).fail(function (e, r) {                console.log("FAIL");            });        }

My only guess right now looking at the URLs is that the PUT url contains %2F and looking at http://www.w3schools.com/tags/ref_urlencode.asp that stands for / which might be causing an issue in the browser? Or maybe I am completely off here and there is some other issue that I am missing.

Edit #1 Adding java code used to generate pre-signed URL

public S3GeneratePresignedUrlDemo(HttpMethod httpMethod) {    this.httpMethod = httpMethod;    System.out.println("HTTP METHOD : " + this.httpMethod);}@Overridepublic void goImpl() throws Exception {            GeneratePresignedUrlRequest request = new GeneratePresignedUrlRequest(bucketName, KEY);    request.setMethod(httpMethod);    request.setExpiration(createDateNHoursFromNow(24));    URL url = s3Client.generatePresignedUrl(request);    System.out.println(url);}private static Date createDateNHoursFromNow(int hours){    Date date = new Date();    long millis = date.getTime();    final int millisInSecond = 1000;    final int secondsInMinute = 60;    final int minutesInHour = 60;    millis += millisInSecond * secondsInMinute * minutesInHour * hours;    date.setTime(millis);    return date;}`