14 years ago
SOAPUI 4.0.1 HTTP URL Header Encoding not able to change
Hello to all.
I have found the following problem with SOAPUI 4.0.1.
the URL encoding type for an HTTP GET request is not possible to be changed.
Example:
creating and HTTP Get request for the following URL:
http://Server_IP/value=1000111200|521000
I have made changes to:
1 - Global SOAPUI Preferences --> HTTP settings --> Preencoded Endpoints --> check
(this is defined as "Do not URL-encode endpoints, set this if your endpoint URLs are already URL-encoded (containing for example %20 or %3A)")
2 - Test Step --> HTTP TestRequest Properties --> Encoding --> "UTF-8" or "iso-8859-1"
using all or any of this options does not have impact and does not change nothing on the behavior of the sending HTTP request.
The pipe "|" always gets encoded into %7C
GET http://Server_IP/value=1000111200%7C521000 HTTP 1.1
How can we set/configure SOAPUI to not change the URL link or to encode into the specific type.
If this is a bug of version 4.0.1 can you please say if it is corrected or working in another version.
Thanks in advance for your answer.
any help is appreciated.
I have found the following problem with SOAPUI 4.0.1.
the URL encoding type for an HTTP GET request is not possible to be changed.
Example:
creating and HTTP Get request for the following URL:
http://Server_IP/value=1000111200|521000
I have made changes to:
1 - Global SOAPUI Preferences --> HTTP settings --> Preencoded Endpoints --> check
(this is defined as "Do not URL-encode endpoints, set this if your endpoint URLs are already URL-encoded (containing for example %20 or %3A)")
2 - Test Step --> HTTP TestRequest Properties --> Encoding --> "UTF-8" or "iso-8859-1"
using all or any of this options does not have impact and does not change nothing on the behavior of the sending HTTP request.
The pipe "|" always gets encoded into %7C
GET http://Server_IP/value=1000111200%7C521000 HTTP 1.1
How can we set/configure SOAPUI to not change the URL link or to encode into the specific type.
If this is a bug of version 4.0.1 can you please say if it is corrected or working in another version.
Thanks in advance for your answer.
any help is appreciated.