How do I create a HTTP Request URL with uppercase characters
I'm trying to create a http request URL with uppercase characters in it but everytime that I try to upper case the Request URL it refeverts to lowercase meaning im unable to connect. This occuring in 5.2.2 but does not occur in 4.6.1
Solved! Go to Solution.
Unfortunately, I have also found the HTTP TestStep UI converting things to lowercase to be a annoying issue!
One workaround is to use a property expansion to set the whole url (e.g. from a project level property) or just the parameters that are case sensitive, thus avoiding having to type the actual url into the HTTP Test Step editor - This is a similar post from a while ago (http://community.smartbear.com/t5/SoapUI-Open-Source/In-HTTP-Test-Requests-only-it-appears-Request-U...
In some cases others have edited the actual project XML file as a workaround!
Hope this helps,
I recommend that you submit this as a product improvement idea in our SoapUI Feature Requests forum. If this idea gets many votes, our team could consider implementing this feature.
SmartBear Community and Education Manager
I think it has already been added as an improvement request:
I have just Kudoed that request, hopefully others will do the same.
I have replied to 3 posts on this topic in my short time on the forum, so hopefully the team will approve it as a request. If they don't approve it, I think it would be really easy to fix in the source code, so maybe I should join the open-source team and volunteer to do the change myself! 🙂
I'm amazed more people haven't had this problem.
I'm currently trying to send an HTTP request with a paramaterized value, however the default value for a project and test suite level paramater are Project and TestSuite respectively.
Accordingly, all of my tests are unable to be paramaterized because SoapUI converts them to lower case and my paramaters aren't found. Is there a simple solution that doesn't require having test-level paramaters for each case?
Just so that you know, there is at least 1 bug raised against this issue:
Plus a feature request too I think.