Forum Discussion
Ton636
13 years agoContributor
Hi, just wanted to let you know that we are also affected by this issue. 4.0.1 works fine, in 4.5 several test cases broke, we had to change the global http parameter "Preencoded Endpoints" and then encode the | char in our template usage.
We are aware that pipes are considered unsafe, unfortunately this is a legacy application that we need to support. A fix for this issue would be most appreciated as we are contemplating rolling back to soapUI 4.0.1 as an alternative.
Ton Vlaming
We are aware that pipes are considered unsafe, unfortunately this is a legacy application that we need to support. A fix for this issue would be most appreciated as we are contemplating rolling back to soapUI 4.0.1 as an alternative.
Ton Vlaming
Related Content
- 8 years agosandrino