V3 Rest 307 Redirects

Answered

Elan Paul

May 05, 2026 17:08

Hello,

We are making a request to the ‘rest/v3/devices’ endpoint and in order to see a response, we need to follow an unusual amount of 307 redirect responses. Usually we have 2 or 3 redirects, but for this account we are seeing dozens of redirects without ever getting to a successful 200. There doesn’t appear to be anything unusual with the account and there are only 100 or so cameras on this account. Can you explain what could be causing so many redirects and how we can fix this?

Thank you

0

• 

  Ichiro

  • Network Optix team

  May 07, 2026 09:42

  Hi,

  Thanks for reaching out. Before we can investigate further, we need a bit more information as what's been shared so far isn't quite enough to pinpoint the cause.

  A couple of clarifying questions:

  1. Are you accessing via the Nx Cloud relay? This is important in determining where the redirects are originating from.

  2. What do you mean by "cameras on this account"? Cameras are associated with a site, not directly with an account. Could you clarify are you referring to a site with approximately 100 cameras? 

      

  On the redirect behavior itself, we haven't been able to observe or reproduce this on our end yet. As a first step, we'd suggest re-authenticating (re-login) and attempting to reproduce the issue, then sharing the results.

  It's also worth noting that there was a required maintenance window that could potentially be relevant depending on your timing. Could you confirm when you first started seeing this behavior?

  Thanks

  0
• 

  Elan Paul

  May 07, 2026 17:04

  Yes Ichiro. We started seeing this issue 2 days ago and are currently still seeing the issue. We have re-authenticated and here is the request and response information:

  Originating request url: https://{guid}.relay.vmsproxy.com/rest/v3/devices

  Response status code: 307

  Response headers: {'Content-Length': '0', 'Date': 'Thu, 07 May 2026 16:49:50 GMT', 'Location': 'https://{guid}.relay-us-chi-1-prod-dp.vmsproxy.com:443/rest/v3/devices', 'Strict-Transport-Security': 'max-age=31536000'}

  The response content, text, and json are empty.

  To answer your questions

  1. Yes we are using Nx Cloud Relay.
  2. Yes, 100 cameras on the site.

  Thank you,

  Elan

  0
• 

  Ichiro

  • Network Optix team

  May 08, 2026 04:54

  Hi Elan,

  I believe there may be a misunderstanding regarding the mechanism, as this behavior is expected.

  An HTTP 307 redirect is a standard and common behavior. The proper implementation is to follow and use the URL provided in the Location header. Please refer to the article, which can help to explain more.

  There is nothing new about this behavior. n fact, this mechanism has been implemented with the Nx Cloud Relay feature was released. So, to clarify:

  1. If you are using Nx Cloud Relay, this behavior is expected and should be properly handled in your implementation. (307 redirect, and forward the authentication header)
  2. The number of cameras or servers within a site is unrelated to this behavior, these are two different components.

  I would recommend following the article and might need a few adjustments on the implementation side.

  Thanks.

  0
• 

  Elan Paul

  May 08, 2026 06:05

  Hi Ichiro,

  Yes, the redirect concept is understood clearly and we handle this case correctly. This is not the issue we are experiencing. The issue is generally there are a few redirects per request - maybe 3 or 4 maximum. On this specific request we were seeing upwards of 25 307 redirects.

  Is there a maximum number of redirects we can expect, so we can handle all requests?

  Is there anything we can do to minimize the number of redirects? Dozens of redirects was unexpected.

  Thank you

  0
• 

  Ichiro

  • Network Optix team

  May 09, 2026 06:14

  Hi 

  Thank you for your follow-up.

  To be transparent: I was not able to reproduce the issue on our end. Before we dig further, a few questions to help narrow this down:

  1. Are you able to reproduce the issue right now?
  2. What was the exact date and time when you first noticed it?
  3. Is the issue still occurring, or did it resolve on its own?

  Just so you're aware, we had several cloud maintenance windows this week. Any systems affected during a downtime period may require a re-login. That could account for the behavior you saw.

  If the issue is still reproducible, please let us share the following :

  • The relay server where you're seeing the issue
  • A specific timestamp when the issue occurred

  That will give us enough to investigate on our end. Thanks for your patience.

  0

Please sign in to leave a comment.