Jump to content


URL Encoding - Accept Spaces


  • Please log in to reply
2 replies to this topic

#1 Guest_Prem Mohan_*

Guest_Prem Mohan_*
  • Guests

Posted 10 July 2008 - 02:01 PM

We are trying to test one of our applications using WAPT.

The application is working fine in Production.
When we run a test script, we are encountering with the error -

HTTP/1.1 400 Bad Request. as a result of the URL
GET /common/getDocument.aspx?pageTitle=New Service Agent&scriptName=../organization/setup_serviceagents.aspx?action=clearcontext HTTP/1.1

The issue is because of space in 'New Service Agent', if we remove the space, then the script works fine. But since its a working application and we have not had this issue in other load testing tools, we do not want to change the code for a successful run and will be a big effort.

Could you please let me know if there is any configuration that could be done in the tool to bypass this encoding check.

#2 Guest_angela_*

Guest_angela_*
  • Guests

Posted 11 July 2008 - 08:14 AM

QUOTE (Prem Mohan @ Jul 10 2008, 09:01 PM) <{POST_SNAPBACK}>
We are trying to test one of our applications using WAPT.

The application is working fine in Production.
When we run a test script, we are encountering with the error -

HTTP/1.1 400 Bad Request. as a result of the URL
GET /common/getDocument.aspx?pageTitle=New Service Agent&scriptName=../organization/setup_serviceagents.aspx?action=clearcontext HTTP/1.1

The issue is because of space in 'New Service Agent', if we remove the space, then the script works fine. But since its a working application and we have not had this issue in other load testing tools, we do not want to change the code for a successful run and will be a big effort.

Could you please let me know if there is any configuration that could be done in the tool to bypass this encoding check.


Do you mean the words "'New Service Agent" in the URL? If so, there should be no spaces between words in the URL.

Please let me know if the option "Encode request parameters" is enabled.

#3 Guest_Paul Deen_*

Guest_Paul Deen_*
  • Guests

Posted 01 August 2008 - 01:18 PM

Strictly speaking this URL is invalid. Why would you expect WAPT to support it?




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users