[JDEV] Firewall jumping

[sean gilman]

It's not that simple.
Depending on the type of http proxy server different things will happen.
The http1.1 spec says that you can pipeline requests.
Therefore you can create a http1.1 session (socket) and send multiple
requests down the pipe. (This sounds good.)
However, some http proxy servers will split each of the pipelined requests
into a new http1.0 request.
As a result the server sees N http1.0 requests instead of a stream of
http1.1 requests.


> -----Original Message-----
> From: jdev-admin at jabber.org [mailto:jdev-admin at jabber.org]On Behalf Of
> Jay, Dylan
> Sent: Thursday, January 20, 2000 5:37 PM
> To: 'Thomas Charron'; jdev at jabber.org
> Cc: Greater NH Linux User Group
> Subject: RE: [JDEV] Firewall jumping
>
>
> > -----Original Message-----
> > From: Thomas Charron [mailto:tcharron at ductape.net]
> > Sent: Friday, January 21, 2000 5:38 AM
> > To: jdev at jabber.org
> > Cc: Greater NH Linux User Group
> > Subject: Re: [JDEV] Firewall jumping
> >
>
> <stuff deleted>
>
> > outgoing XML data that it needs to send,
> > and the server would then pass all data back thru the HTTP
> > connection that it
> > has in it's buffer for the client.
> >
> >   The server would be configured to require a client
> > connection ever X seconds,
> > X being a configurable parameter
>
> This all sounds great, but why not just let the http session stay
> connected.
> I believe nothing in the protocol prevents continuing
> communication in both
> directions. Let the connection stay until it gets cut (as some
> proxies maybe
> inclined to do) and then do the reconnected within X seconds routine.
>
>
> > dependant on the server.  If a client had not reconnected
> > within X timeframe,
> > the user would be marked offline, all
> > pooled output stored offline, and the sessionID expired.
> > When the client
> > reconnects AFTER the timeout, either a message
> > stating the connection has expired, with an immediate
> > disconnection, or a
> > reauthentication process of some sort could
> > take place to reactivate the sessionID.
> >
> >   An example of the HTTP conversation is below:
> > ************************************
> > * INITIAL CONNECTION CONVERSATION: *
> > ************************************
> > --------------------------------------------------
> > Client:
> >
> > GET /auth HTTP/1.0
> > -------------------------
> > Server:
> >
> > HTTP/1.0 200 OK
> > Date: Wednesday, 02-Feb-95 23:04:12 GMT
> > Server: Jabber/1.0-dev
> > Last-modified: Monday, 31-Jan-2000 23:33:16 GMT
> > Content-type: text/XML
> > Content-length: 2345
> >      * a blank line *
> > sessionID=hgGFG798ghj65HUgf
> > --------------------------------------------------
> >
> > ****************************************
> > * SUBSEQUENT CONNECTION CONVERSATIONS: *
> > ****************************************
> > --------------------------------------------------
> > Client:
> >
> > POST /converse HTTP/1.0
> > User-Agent:  libwww/2.14
> > From:  Stars at WDVL.com
> > Content-type: application/x-www-form-urlencoded
> > Content-length: 150
> >      * a blank line *
> > sessionID=hgGFG798ghj65HUgf
> > &XML=<message ID="789367124"/>
> > -----------------------
> > Server:
> >
> > HTTP/1.0 200 OK
> > Date: Wednesday, 02-Feb-95 23:04:12 GMT
> > Server: Jabber/1.0-dev
> > Last-modified: Monday, 31-Jan-2000 23:33:16 GMT
> > Content-type: text/XML
> > Content-length: 2345
> >      * a blank line *
> > <something type="some xml packets for the client"/>
> > --------------------------------------------------
> >
> >   What's everyone think about this framework?
> >
> > ---
> > Thomas Charron
> > << Wanted: One decent sig >>
> > << Preferably litle used  >>
> > << and stored in garage.  ?>>
> >
>
> _______________________________________________
> jdev mailing list
> jdev at jabber.org
> http://mailman.jabber.org/listinfo/jdev
>