Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: "J.O. Aho" <user@example.net>
Newsgroups: comp.lang.php
Subject: Re: simplexml_load_string problem
Date: Sat, 11 Sep 2021 21:31:47 +0200
Lines: 22
Message-ID: <iq4eh4Fo96mU1@mid.individual.net>
References: <shckdp$1uo2$1@gioia.aioe.org> <ipuh7qFjqe9U1@mid.individual.net> <shin2r$1ij$2@gioia.aioe.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Trace: individual.net 6l4wpAlTI3KTyO2oAlr6Zgo3oAPGzCSxna9KGuJsFJdrpA6zq9
Cancel-Lock: sha1:quUoZAGx0vatoStISOCXgCR3J4s=
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.1.0
Content-Language: en-US-large
In-Reply-To: <shin2r$1ij$2@gioia.aioe.org>
Xref: csiph.com comp.lang.php:18792

On 11/09/2021 18.55, Torakiki wrote:
>> This may be a case of your data is url-decoded when posted and the + 
>> is then also decoded to space as it should be according to standard.
> 
> The XML file comes to me from an external company that uses Python, but 
> they assured me that the file is only base64 encode
> 
+ is a character allowed in base64, when the whole xml is url-decoded, 
the + in the base64 code will be translated to space.

Sending the file with post is a bad option, you should have made it to 
use put instead.

Work around would be to url-encode the file before you base64 decode it 
to get back the +.


-- 

  //Aho