hmpatel / rest-assured

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

URL always has an explicit port set #381

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Any request with or without explicit port set will result in an URL that has 
an explicit port set.

What is the expected output? What do you see instead?
I would like to be able to produce an URL of the form 
http://somehost/someResource.
I always see http://somehost:somePort/someResource.

What version of the product are you using? On what operating system?
We use 2.3.4. on Ubuntu 12.04.4.

Please provide any additional information below.
This 'problem' was raised because we have some very special mod_rewrite rules 
that work on :80 but not without port. This is of course a minor issue but I 
still think it should be able to select no explicit port to check that the 
server actually handles the default port mapping properly?!

Thx a lot for rest-assured,
Oliver Schneider
Junior QA Engineer
olsc@spreadshirt.net

Original issue reported on code.google.com by o...@spreadshirt.net on 9 Jan 2015 at 3:51

GoogleCodeExporter commented 9 years ago
Hmm interesting. REST Assured automatically adds a port. I think this use case 
i so narrow and the changes I have to make in the code so large and complex 
(probably) that I don't think it's worth this. I think it's better if you could 
change the mod_rewrite_rules since I suppose they should handle a port as well?

Btw I like spreadshirt :)

Original comment by johan.ha...@gmail.com on 16 Mar 2015 at 11:02