Ask a Question

[Ready API 1.2] Double slash (//) in path

marcl
Occasional Contributor

[Ready API 1.2] Double slash (//) in path

I get a "double slash" error when calling a REST method using GET. Note that I have lots of other REST calls in my project which do not seems to trigger this bug.

Any idea where the error is coming from and/or how I can identify the cause of the problem ?

 

 

Thu Jul 16 13:05:50 UTC 2015:ERROR:nu.xom.MalformedURIException: Double slash (//) in path
   nu.xom.MalformedURIException: Double slash (//) in path
   	at nu.xom.Verifier.throwMalformedURIException(Verifier.java:161)
   	at nu.xom.Verifier.checkPath(Verifier.java:396)
   	at nu.xom.Verifier.checkAbsoluteURIReference(Verifier.java:907)
   	at nu.xom.Element._setNamespaceURI(Element.java:869)
   	at nu.xom.Element.setNamespaceURI(Element.java:852)
   	at com.eviware.soapui.impl.rest.support.handlers.JsonXmlSerializer.processJSONObject(JsonXmlSerializer.java:973)
   	at com.eviware.soapui.impl.rest.support.handlers.JsonXmlSerializer.write(JsonXmlSerializer.java:649)
   	at com.eviware.soapui.impl.rest.support.handlers.JsonXmlSerializer.write(JsonXmlSerializer.java:616)
   	at com.eviware.soapui.impl.rest.support.handlers.JsonMediaTypeHandler.createXmlRepresentation(JsonMediaTypeHandler.java:61)
   	at com.eviware.soapui.impl.wsdl.submit.transports.http.BaseHttpResponse.getContentAsXml(BaseHttpResponse.java:382)
   	at com.eviware.soapui.impl.rest.panels.request.inspectors.schema.InferredSchemaInspector.afterSubmit(InferredSchemaInspector.java:106)
   	at com.eviware.soapui.impl.wsdl.WsdlSubmit.notifyListenersAfterSubmit(WsdlSubmit.java:102)
   	at com.eviware.soapui.impl.wsdl.WsdlSubmit.run(WsdlSubmit.java:143)
   	at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
   	at java.util.concurrent.FutureTask.run(Unknown Source)
   	at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
   	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
   	at java.lang.Thread.run(Unknown Source)

 

The request causing the problem is the following

 

GET http://myhost:42221/doit HTTP/1.1
Accept-Encoding: gzip,deflate
Host: myhost:42221
Connection: Keep-Alive
User-Agent: Apache-HttpClient/4.3.1 (java 1.5)

 

And the received answer contains this:

 

HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: 13

{"success":1}

 

 

16 REPLIES 16
johandelaat
Occasional Contributor

Hi,

I'm using Ready! API 1.3.1 - SoapUI NG and experience the same problem.

 

I'm doing a call where in the resource/Method there is a reference to a custom Properety of the TestCase (.../${#TestCase#sourceCode}/...).

Now it looks like if this reference is not used and thus an ERROR:nu.xcom.MalformedURIException: Double slash (//) in path is trown.

BUT the step is executed correctly, with the correct value of the properety and giving the expected result.

 

So where is this ERROR comming from?

On the forum I've read it's a known bug.

Any idea what triggers this error and how to avoid it?

Any idea when it wil be fixed?

 

Johan 

Please see if the following link helps, which says that resouce url having trailing slashes could cause this issue.
http://forum.soapui.org/viewtopic.php?f=13&t=24704


Regards,
Rao.
marcl
Occasional Contributor

Hello Rao,

 

I'm aware of this bug (although I hope it's fixed, given how old it is), but there's no trailing slash in my request at least.

GET http://myhost:42221/doit HTTP/1.1

Thanks!

Marc

johandelaat
Occasional Contributor

Rao,

 

Idem dito for me : no trailing slashes.

As mentioned in my post the call is executed as expected.

It's only annoying that false errors are logged.

 

Johan

blade
Occasional Contributor

Hi,

 

Has there been any update from smartbear on this issue? I am currently getting this error in Ready API 1.5.0. Will this be addressed in the next release? It has a downstream impact that when I run a Test Case, upon reaching the last step it takes approx 15-20 seconds to complete.

 

 

marcl
Occasional Contributor

Nope, on news on my side 😕

Hebla
Occasional Contributor

I'm having the same problem. We run the integration testsuite as part of a Jenkins pipeline, and build will be blocked if the soapui project fails. Now it fails always because of this error...

 

Any update on this would be greatly appresiated.

Same here !

Happens on the "SoapUI" Free version.

I Was thinking of upgrade yet i see no benefit as the paid version has the same issues.

 

Please fix as i can find dozens of reports like these since 2009

I too read lot of times people saying this.
But, any steps to reproduce this issue?


Regards,
Rao.
cancel
Showing results for 
Search instead for 
Did you mean: