Forum Discussion

do_shanahan's avatar
do_shanahan
New Contributor
4 years ago

Issue with 301 redirect to one of your maven URLs

Hi there,

 

Apologies if this is the wrong location to post this message. If it is please could I ask someone to redirect it to the appropriate forum location. We are observing a random failure to the URL https://rapi.tools.ops.smartbear.io/nexus/content/groups/public/ as described below.

 

We have a legacy repository configured to use this URL http://www.soapui.org/repository/maven2/.

When attempting to access it the www.soapui.org server generates a 301 http redirect to a smart bear maven 2 repository URL https://rapi.tools.ops.smartbear.io/nexus/content/groups/public/ (see example curl output from below)

 

curl -X GET http://www.soapui.org/repository/maven2/
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>301 Moved Permanently</title>
</head><body>
<h1>Moved Permanently</h1><p>The document has moved <a href="https://rapi.tools.ops.smartbear.io/nexus/content/groups/public/">here</a>.</p>
</body></html>

 

The domain from the URL rapi.tools.ops.smartbear.io appears to be configured with DNS round robin with two IP addresses configured as follows. 

 

nslookup rapi.tools.ops.smartbear.io
Server: 127.0.0.53
Address: 127.0.0.53#53

Non-authoritative answer:
Name: rapi.tools.ops.smartbear.io
Address: 34.234.41.215
Name: rapi.tools.ops.smartbear.io
Address: 3.220.159.57

 

We see that only one of these IP addresses e.g. 34.234.41.215 is working while the 2nd appears to be unresponsive.

 

This curl produces a 200 http response from IP 34.234.41.215

 

curl -ik -X GET https://34.234.41.215/nexus/content/groups/public/ | grep HTTP/2
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0HTTP/2 200
100 362k 0 362k 0 0 325k 0 --:--:-- 0:00:01 --:--:-- 325k

 

However the following curl from IP 3.220.159.57 times out 

time curl --connect-timeout 30 -vvv -ik -X GET https://3.220.159.57/nexus/content/groups/public/
Note: Unnecessary use of -X or --request, GET is already inferred.
* Trying 3.220.159.57:443...
* Connection timed out after 30001 milliseconds
* Closing connection 0
curl: (28) Connection timed out after 30001 milliseconds

real 0m30.008s
user 0m0.008s
sys 0m0.000s

 

Would you please have someone from your technical team take a look and resolving the issue with the unresponsive IP address.

 

Regards,


Declan O'Shanahan

No RepliesBe the first to reply