It started as small proxy to handle special cases when we need access to
private LAN inside our LAN to provision some servers via WEB. I never
intended to make it full HTTP proxy but even in current state it does
work and we access our appliance boxes though this module.
To make it more
On 9/18/06, Vlad Seryakov [EMAIL PROTECTED] wrote:
It started as small proxy to handle special cases when we need access to
private LAN inside our LAN to provision some servers via WEB. I never
intended to make it full HTTP proxy but even in current state it does
work and we access our appliance
Because this has never been exposed to Tcl before, and because seems
to be (to me) a genuine bug which could bight us as we add more HTTP
1.1 support, it seems like now would be the time to take a step back
and look at what we really want in this API.
It's only one call to register, one to
I don't know, I'm asking...
I was wondering why registering a proxy handler is different than a
regular registered proc. Do they have to be different?
The main difference seems to be that you can register a proxy for a
protocol, i.e. http or https, but you don't have that option with
regular
On 9/18/06, Vlad Seryakov [EMAIL PROTECTED] wrote:
I don't know, I'm asking...
I was wondering why registering a proxy handler is different than a
regular registered proc. Do they have to be different?
The main difference seems to be that you can register a proxy for a
protocol, i.e.
It will require 2 hash calls but currently it results in error, so 2
calls will not be that bad if default handler will be able to process
request.
Stephen Deasey wrote:
On 9/18/06, Vlad Seryakov [EMAIL PROTECTED] wrote:
I don't know, I'm asking...
I was wondering why registering a proxy
On 9/18/06, Stephen Deasey [EMAIL PROTECTED] wrote:
I was wondering why registering a proxy handler is different than a
regular registered proc. Do they have to be different?
As I've been reading the NaviServer sources to acquaint myself I was
wondering the same thing.
The main difference
