Hi!Phfew! Finally fixed this crap. Not exactly fixed, but worked around it. The solution was to put this on the vhost definition:
SSLOptions -FakeBasicAuth -ExportCertData -StrictRequire -StdEnvVarsThis way, no SSL info is sent from Apache to the app, and the problem does not occur.
Still, the question remains, what the heck is wrong here? Yours Miguel Arroz On 2009/02/14, at 18:02, Miguel Arroz wrote:
Hi! I'm having severe problems making WO work on FreeBSD with SSL.There was a thread some time ago that suggested to change the adaptor code to disable client side certificates, but even so it doesn't work.I have sniffed the data that is sent between Apache and the app. On the client side certificate, I get this:SSL_CLIENT_CERT:.abortive.accurate.standard.unclean.SSL Proxy connect failed.reason unknown.SSL input filter read failed..TLS/ 1.0.Connection: Upgrade.Upgrade: TLS/1.0, HTTP/1.1.filling buffer.APR output filter.APR input filter.%s: %s %ld/%d bytes %s BIO# %pp [mem: %pp] %s.... + -------------------------------------------------------------------------+ .%s: I/O error, %d bytes expected to %s on BIO#%pp [mem: %pp]....read from buffered SSLThe WOAdaptor debug is as follows (this is from the Wonder recent plugin, but it's similar to the FreeBSD port one with the code patched to disable client side certificates):Debug: <WebObjects Apache Module> new translate: /WO/WebObjects/ Survs.woa/wa/signIn Info: <WebObjects Apache Module> new request: /WO/WebObjects/ Survs.woa/wa/signInDebug: App Name: Survs.woa/wa/signIn (5) Info: V4 URL: /WO/WebObjects/Survs.woa/wa/signIn Info: Selected new app instance at index 0 Debug: Composed URL to '/WO/WebObjects/Survs.woa/1/wa/signIn' Info: New request is GET /WO/WebObjects/Survs.woa/1/wa/signIn HTTP/1.1 Info: Sending request to instance number 1, port 2001 Info: Trying to contact Survs:1 on (2001) Info: attempting to connect to 192.168.2.210 on port 2001 Info: Survs:1 on (2001) connected [pooled: No]Error: sendBuffers(): send error: Invalid argument <----------------------------------- I believe here's the problemError: error sending request Error: Failed to send request Info: Marking instance 1 dead Warn: Marking 192.168.2.210:1 unresponsive Debug: connectionAttempts = 1, retries = 10 Info: Reading configuration from http://192.168.2.210:1085/WebObjects/wotaskd.woa/wa/woconfig Info: attempting to connect to 192.168.2.210 on port 1085 Info: Preparing to read config for host: 192.168.2.210 Info: New response: HTTP/1.0 200 Apple WebObjects Info: tr_selectInstance(): scheduler failed to select instance. Info: No new instance located for failover Error: Request handling error: No instance availableDoes anyone know how to fix this? I'm trying to solve this since yesterday, and I'm getting really, really pissed off.What pisses me off the most is that in our production and stage server, this works perfectly (the first with a "real" certificate, the second with a self-signed one). The problem is happening on a FreeBSD virtual machine under Parallels. Everything is working fine but this.Please help! Yours Miguel Arroz ........................... http://www.survs.com _______________________________________________ Do not post admin requests to the list. They will be ignored.Webobjects-deploy mailing list (Webobjects- [email protected])Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-deploy/arroz%40guiamac.com This email sent to [email protected]
........................... http://www.survs.com
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-deploy mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-deploy/archive%40mail-archive.com This email sent to [email protected]
