Allow uppercase in URL in the HTTP Request test step

Allow uppercase in URL in the HTTP Request test step

In soapUI 5.2.2 I have to use a property or modify the xml file directly to be able to test against a URL with mixed case it should just be allowed. Refer to Question on How for the the workaround i want to avoid

This feature request has been implemented in version 5.3 (shown in Bug Fix section 'A bug fix by bearsoftware (GitHub nickname): The Request URL property of the HTTP Request test step did not allow capital letters. (SOAPUIOS-213)')

Please can you move this feature request to status of 'implemented'? Sorry, if you're not the right person to do this.

Also, please can I check that https://sourceforge.net/p/soapui/bugs/ is the right place to log/discuss SoapUI O/S bugs? I sometimes wonder about picking these up but am not sure if this is the right place.

I believe that sourceforge.net may be not the right place any more from my understand as SoapUI source has been moved / relocated to github which might allow to create issue there. Of course, looking forward to hear from @TanyaGorbunova.

For those do not aware workaround for this issue:

By the way, there is simple & clean workaround for this issue if property expansion for the url is used, where capital letter can be supplied which won't be replaced to small.

Thanks for the feedback. As far as I am aware, there is no issue tracking feature in the SoapUI GitHub project - the only correct course of action in GitHub is to code a fix/enhancement and create a 'pull request', which is not the same as having a means to track issues that may or may not be developed.

I also wanted to check with @TanyaGorbunova, who manages the 'Feature Requests' area, as I think it's a nice area and a good way to empower community members to contribute ideas, even if they aren't able to provide solutions. Updating a few statuses might help demonstrate progress and encourage more contribution.

Thanks for the workaround (which is also detailed in the initial feature request), but there is no need for any work-around - as my fix has been accepted, merged and deployed as part of release 5.3.

You're quite correct in that one needs to become a contributor before contributing code (as I am already), but that doesn't give permissions to commit directly to the GotHub repository, or at least not in my case. Instead you need to create pull requests and a member of SmartBear then merges your code. As for that GitHub issue tracker it appears unused anyway.