Re: Connecting to the exterior network is impossible `directly'
On Sun, 04 Jul 2010 11:12:34 +0200
Merciadri Luca <Luca.Merciadri@student.ulg.ac.be> wrote:
> Celejar wrote:
> > >From http://en.wikipedia.org/wiki/Captive_portal#Implementation
> > -----
> > Implementation
> > There is more than one way to implement a captive portal.
> >  Redirection by HTTP
> > If an unauthenticated client requests a website, DNS is queried by the
> > browser and the appropriate IP resolved as usual. The browser then
> > sends an HTTP request to that IP address. This request, however, is
> > intercepted by a firewall and forwarded to a redirect server. This
> > redirect server responds with a regular HTTP response which contains
> > HTTP status code 302 to redirect the client to the Captive Portal.
> Is the 302 status code standardized? (I'm here dealing with CISCO
> routers and network stuff, and do they use 302 too?)
302 is a standard (but see the page below) redirect code; I have no
experience with Cisco gear:
foffl.sourceforge.net - Feeds OFFLine, an offline RSS/Atom aggregator
mailmin.sourceforge.net - remote access via secure (OpenPGP) email
ssuds.sourceforge.net - A Simple Sudoku Solver and Generator