search

hmpatel / rest-assured

Automatically exported from code.google.com/p/rest-assured
0 stars 0 forks source link

Request specification overrides port from base url #378

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
I am using a RequestSpecification to specify the accept and content-type 
headers. I do not set the port in the request spec.

When using a non default port and setting the baseURI port 80 seems to  be used 
from the request specification.

When setting the requestContentType and responseContentType (with the 
deprecated setters) and not using the request specification it works as 
expected.

I suggest to either un-deprecate the setter and make a documentation note the 
request specification or merge the configuration from baseURI and request 
specification.

Original issue reported on code.google.com by everf...@gmail.com on 7 Dec 2014 at 1:57

GoogleCodeExporter commented 9 years ago 
This is probably a bug in the merging of request specifications

Original comment by johan.ha...@gmail.com on 30 Dec 2014 at 9:04

GoogleCodeExporter commented 9 years ago 
I'm trying to reproduce this but I can't. You you provide a code example of 
your test?

Original comment by johan.ha...@gmail.com on 17 Mar 2015 at 11:39

GoogleCodeExporter commented 9 years ago 
I assume this was fixed in the mean time, I switched to request spec and could 
not rep produce the issue.

Original comment by everf...@gmail.com on 17 Mar 2015 at 11:46