On 12 Jul '08, at 9:25 PM, [EMAIL PROTECTED] wrote:
Is there some content type I could use other than "application/x-www-
form-urlencoded" that would work with PHP scripts?
You can use any content-type you like, but your PHP script will then
have to read the data from the input stream itsel
On Jul 13, 2008, at 12:25 AM, [EMAIL PROTECTED] wrote:
-- Original message --
From: Stefan Arentz <[EMAIL PROTECTED]>
If you want to send Base64 encoded data in a query parameter (or post
data) then you will need to 'percentage-escape' it properly. In which
-- Original message --
From: Stefan Arentz <[EMAIL PROTECTED]>
>
If you want to send Base64 encoded data in a query parameter (or post
> data) then you will need to 'percentage-escape' it properly. In which
> case a '+' needs to be translated to a '%2b'.
>
I
-- Original message --
From: Stefan Arentz <[EMAIL PROTECTED]>
>
> If you want to send Base64 encoded data in a query parameter (or post
> data) then you will need to 'percentage-escape' it properly. In which
> case a '+' needs to be translated to a '%2b'.
B
On Jul 12, 2008, at 10:17 PM, [EMAIL PROTECTED] wrote:
Hi
I wrote a class (PHPInvocation) that handles all the nitty gritty
details of preparing NSURLRequests, NSURLConnections etc for calls
to PHP scripts, but have run across this nasty bug. What's happening
is that somewhere between th
On Jul 12, 2008, at 7:17 PM, [EMAIL PROTECTED] wrote:
I don't know if this is a Cocoa problem or a PHP problem but does
anyone know if or why Cocoa would do this conversion? If it is a
Cocoa "feature" how would I make it preserve the data exactly as
it's given?
The first thing I'd do is us
Hi
I wrote a class (PHPInvocation) that handles all the nitty gritty details of
preparing NSURLRequests, NSURLConnections etc for calls to PHP scripts, but
have run across this nasty bug. What's happening is that somewhere between the
creation of an NSURLConnection and the target PHP script, "+
