Re^3: PSGI, Plack et.al.

I really like Gepok. For Starman etc the advice is to place an HTTPS proxy (e.g. Apache) in front of the server. However, that means that the server misses out on all the transactional information in the HTTPS connection, such as client certificates. Gepok has the HTTPS built in, so you can use HTTPS certificates for authentication.

perl -E'sub Monkey::do{say$_,for@_,do{($monkey=[caller(0)]->[3])=~s{::}{ }and$monkey}}"Monkey say"->Monkey::do'

Comment on Re^3: PSGI, Plack et.al.

Replies are listed 'Best First'.
Re^4: PSGI, Plack et.al. by Anonymous Monk on Oct 24, 2012 at 16:13 UTC
However, that means that the server misses out on all the transactional information in the HTTPS connection, such as client certificates. Sounds fishy, it doesn't look from the docs like Gepok does anything more than Perlbal in terms of ssl suport	[reply]
Re^5: PSGI, Plack et.al. by tobyink (Canon) on Oct 24, 2012 at 21:17 UTC
I can't comment on Perlbal, but for my particular usage, Gepok's ssl_verify_mode and ssl_verify_callback options were useful. Indeed, I wrote the patch to implement them and submitted it to Gepok's author. Also useful is `$env->{'gepok.socket'}` being available to PSGI applications. `perl -E'sub Monkey::do{say$_,for@_,do{($monkey=[caller(0)]->[3])=~s{::}{ }and$monkey}}"Monkey say"->Monkey::do'`	[reply] [d/l]