Thanks for the quick repsonse Giscard. The FollowRedirects option is set to true. I also tested setting it to false (to check if it does affect anything). This results in not following the 301 at all. So changing the option itself works
. But this does not solve the problem.
The Location header of the first reponse (the 301 response) points to another URL, with another domain (geodata.nationaalgeoregister.nl) than the original request. SoapUI seems to recognize that it is a 301 redirect, because it creates another HTTP request. This HTTP request does use the correct path of the Location header. But still uses the domain of the first, original request (
www.nationaalgeoregister.nl instead of geodata.nationaalgeoregister.nl). It seems like SoapUI is inspecting the value of the Location header and uses only the path of the URL, while it should use the entire URL.
I tried it for the following HTTP requests/responses:
a 301 :
http://www.nationaalgeoregister.nl/geon ... anguage=nl which redirects to:
http://geodata.nationaalgeoregister.nl/ ... ik2008.zipa 302 :
http://newsonmaps.com/obj/statistiek/gr ... ten/GM0400 this one redirects to
http://geodata.nationaalgeoregister.nl/ ... e='GM0400')
a 302:
http://newsonmaps.com/bgi/ which redirects to
http://brentjensgeoict.nl/contact/ In all cases, using wget I do get the correct responses, but using SoapUI the path of the redirect is used, but not the domain. So for the 3rd example, the following HTTP request is sent:
http://newsonmaps.com/contact/instead of:
http://brentjensgeoict.nl/contact/I saw in the HTTP log that a cookie is set, also for the domain. Could this affect the result? And how to solve this?
