NAS-ID in the redirected HTTP

  • 1
  • Question
  • Updated 5 years ago
  • Answered
"Aerohive devices now include the NAS-ID in the redirected HTTP headers sent to external captive web portals so that you can use the information to determine the Aerohive device to which a captive web portal client is associated." 6.1r2

does anyone know what the httpheader key is when pointing the external captive web portal to an external website location so that the location of the aerohive ap can be identified - what is its http key and name so I can access it via html/javascript/asp.net

Thanks, Paul
Photo of Paul Bowker

Paul Bowker

  • 21 Posts
  • 1 Reply Like
  • excited

Posted 5 years ago

  • 1
Photo of Sarah Banks

Sarah Banks

  • 75 Posts
  • 4 Reply Likes
Hi Paul, I don't understand what you mean by an HTTP Header key is, but if you want to understand what the URL looks like coming from the AP, so that you could parse it correctly, an easy way to do this is to enable this feature and take a look at the URL. IIRC it embeds into the URI as NAS-ID=some.ip.addy.here and IIRC again, you can parse on the &. Did I completely misunderstand your question? :)
Photo of Paul Bowker

Paul Bowker

  • 21 Posts
  • 1 Reply Like
Hi Sarah,

Really appreciate the reply, the httpheaders are embedded pieces of information that are sent within the html package sent to the browser, as I understand Aerohive have injected a custom HTTPHeader into the html package with the NAS-ID, what I want to understand is when in the process of the captive web portal submission (user attaches to public hotspot, user is presented with CWP splash page saying ‘click to accept’, user gets redirected to appropriate internet website once clicked button) that the NAS-ID is accessible and how is it identified.

For example is the NAS-ID available to the browser through the HTTPHeader when the user first gets presented with the CWP splash page (‘please click button to accept’) or is the NAS-ID sent through the HTTPHeaders once the user has accepted and then gets redirected. My fingers are crossed that it is the former as this will allow me to know where the user is (because I can grab the NAS-ID and hence the location of the access point) when the user first enters the CWP.

Hope that explains a bit better.
Photo of Sarah Banks

Sarah Banks

  • 75 Posts
  • 4 Reply Likes
Hi Paul,
Today, the NAS-ID information is inserted as the redirection takes place; not in the initial presentation of the page. I can guess what your next comment will be, and I take your feedback and the desire to have this information presented initially when the user connects and is presented the CWP splash page, and will work with engineering accordingly. :) Thanks for the feedback!
Photo of Paul Bowker

Paul Bowker

  • 21 Posts
  • 1 Reply Like
Hi Sarah,

Thanks for that and I very much look forward to having the id of the access point available on the presentation of the captive web portal initial splash page - it will solve a very big problem for me.

Kind Regards
Paul