i seem to remember someone in here uses weechat, like me...
i tried it out the other day.
but i dont use split windows much, so ill stick with irssi for the time being
obsidieth: yeah, vertical split windows is why i switched away from irssi and to weechat
also, weechat's plugin arch is super nice.  very easy to write plugins, and can be done in C, Perl, Python, Ruby, and Lua
instead of just Perl w/ irssi
yeah i might have to give er another look
certainly looks powerfull, but i dont like change
right
ok sleep time, later
later
pz
Any Apache gods in here?
mhoran: i've used it a lot, but not a god
I'm having some reverse proxy issues.
My app server sometimes redirects users from an SSL link to a non-SSL link with the Location header and status 203.
302, rather.
ProxyPassReverse doesn't work in this instance, because the Location header is replaced with the server name of the current virtual host.
So, the desired behavior is, when this redirect is triggered in the SSL vhost, redirection to the non-SSL vhost.
I can't tell if that's possible.
(phone meeting)
We push that into the app instead of at Apache. I don't know if we do that because we're lazy or because it's impossible otherwise.
That's basically what I did. This issue was triggered because we used to run the app server on ports 80 and 443, listening on 127 addresses. This proved to be a problem in our DR scenario, because Apache was configured to listen only on the external IP, meaning it'd have to be changed in a disaster situation.
So I hacked the app server code to drop the port numbers.
But that's a total hack.
The other solution I just came up with is to use ProxyPassReverse /nossl <url to replace> and then a RewriteRule for the corresponding Location header in the SSL vhost.
However, that results in an extra 302 redirect ...
Really, I want a substitute and replace for Location headers.
I think I'm going to go with the ProxyPassReverse and RewriteRule, instead of hackign the OpenACS code.
You should blog about it after you figure it out. Save everyone the struggle later.
mhoran: IMO, I'd put that behavior in app code, b/c if it is a hard requirement, it can be unit tested within app code.  If it is not in app code, your app could pass all unit tests, but a mis-configuration of apache breaks it
how's it hangin in here
'sup