Alain Verleyen: I suppose the index.php is
your code ? Are you using urldecode()?
The only relevant question at this point is why is WebRequest mutating encoded urls before forwarding them to the server. Choice of webserver
is irrelevant.
The only relevant question at this point is why is WebRequest mutating encoded urls before forwarding them to the server. Choice of
webserver is irrelevant.
At my request it was recognize as a bug by Metaquotes and fixed (at least for this specific issue using a '+', I have no details about what was
done exactly).
At my request it was recognize as a bug by Metaquotes and fixed (at least for this specific issue using a '+', I have no details about what was done exactly).
Dear Alain, Thanks, I didn't check the topic, during a new search for a feature in MQL, I ended up in this thread again, and I saw your post, your time spent on this issue is appreciated, the issue is resolved in MQL5 version, but still not in MQL4.
Allow the use of cookies to log in to the MQL5.com website.
Please enable the necessary setting in your browser, otherwise you will not be able to log in.
You are signed in. Two-factor authentication has been disabled. Set it up again and scan a new QR code, or continue with two-factor authentication disabled.
The server is PHP, the most common server (78.6%) according to https://w3techs.com/technologies/overview/programming_language
I suppose the index.php is your code ? Are you using urldecode()?
The only relevant question at this point is why is WebRequest mutating encoded urls before forwarding them to the server. Choice of webserver is irrelevant.
I suppose the index.php is your code ? Are you using urldecode()?
No, here's the .php code:
The only relevant question at this point is why is WebRequest mutating encoded urls before forwarding them to the server. Choice of webserver is irrelevant.
I agree.
At least, developer should be able to select to let WebRequest do encoding or leave the request untouched.
I agree.
Ok as you want. If you are not interested by a solution it's fine for me. I lost enough time on this topic.
I have managed to use POST method, but not always I have permission to manage the code at server side.
Ok as you want. If you are not interested by a solution it's fine for me. I lost enough time on this topic.
What is the solution?
At my request it was recognize as a bug by Metaquotes and fixed (at least for this specific issue using a '+', I have no details about what was done exactly).
Build 2461. This code gives now :
At my request it was recognize as a bug by Metaquotes and fixed (at least for this specific issue using a '+', I have no details about what was done exactly).
Build 2461. This code gives now :
Dear Alain,
Thanks, I didn't check the topic, during a new search for a feature in MQL, I ended up in this thread again, and I saw your post, your time spent on this issue is appreciated, the issue is resolved in MQL5 version, but still not in MQL4.