Skip to main content

Sending encoded XML to a server from iPhone



I'm communicating between an iPhone app and a server using XML. To get around the problem of the user entering any character that might break the XML before I send it to the server i'm using the NSString method:







[string stringByAddingPercentEscapesUsingEncoding:NSUTF8StringEncoding];







But I noticed when doing a log of the string that the & symbol is not escaped? I thought that it should be? spaces, quotation marks and hash symbols which I've tested for all encode fine but not the ampersands?





What is the most common methods used for encoding/decoding XML sent to/received from a server?





Thanks.


Comments

  1. The answer provided by @sleepy is a good approach, or if you prefer the syntax of implementing this in a category see this link for an example.

    Note that you should need to do this only for characters you are sending to the server via the URL parameters. If you are actually POST'ing XML data to the service by placing the XML content into the HTTP body of your request, then this kind of encoding is not needed. Depending on the size of the XML to be posted and the interface supported by your service, using the HTTP body might be a better choice in some scenarios.

    As an example of how to do this in the HTTP body, I typically use something like this:

    NSData *requestData = [requestXml dataUsingEncoding:NSUTF8StringEncoding];
    NSString *requestLength = [NSString stringWithFormat:@"%d", [requestXml length]];
    NSMutableURLRequest *request = [NSMutableURLRequest requestWithURL:serviceURL];
    [request setHTTPMethod:@"POST"];
    [request setValue:@"text/xml" forHTTPHeaderField:@"Content-Type"];
    [request setValue:requestLength forHTTPHeaderField:@"Content-Length"];
    [request setHTTPBody:requestData];


    where requestXML is an NSString containing the XML I want to post and serviceURL is an NSURL for the service URL. In this case I am using UTF encoding for my XML content, which is what you should probably be using in all cases unless you have a specific reason not to.

    ReplyDelete
  2. I assume you are POSTing the data. You can use the following function for escaping the XML data:

    +(NSString *)urlEncode:(NSString *)str {
    return (NSString *)CFURLCreateStringByAddingPercentEscapes(NULL,
    (CFStringRef)str,
    NULL,
    (CFStringRef)@"!*'\"();:@&=+$,/?%#[]% ",
    CFStringConvertNSStringEncodingToEncoding(NSUTF8StringEncoding));
    }

    ReplyDelete

Post a Comment

Popular posts from this blog

[韓日関係] 首相含む大幅な内閣改造の可能性…早ければ来月10日ごろ=韓国

div not scrolling properly with slimScroll plugin

I am using the slimScroll plugin for jQuery by Piotr Rochala Which is a great plugin for nice scrollbars on most browsers but I am stuck because I am using it for a chat box and whenever the user appends new text to the boxit does scroll using the .scrollTop() method however the plugin's scrollbar doesnt scroll with it and when the user wants to look though the chat history it will start scrolling from near the top. I have made a quick demo of my situation http://jsfiddle.net/DY9CT/2/ Does anyone know how to solve this problem?

Why does this javascript based printing cause Safari to refresh the page?

The page I am working on has a javascript function executed to print parts of the page. For some reason, printing in Safari, causes the window to somehow update. I say somehow, because it does not really refresh as in reload the page, but rather it starts the "rendering" of the page from start, i.e. scroll to top, flash animations start from 0, and so forth. The effect is reproduced by this fiddle: http://jsfiddle.net/fYmnB/ Clicking the print button and finishing or cancelling a print in Safari causes the screen to "go white" for a sec, which in my real website manifests itself as something "like" a reload. While running print button with, let's say, Firefox, just opens and closes the print dialogue without affecting the fiddle page in any way. Is there something with my way of calling the browsers print method that causes this, or how can it be explained - and preferably, avoided? P.S.: On my real site the same occurs with Chrome. In the ex