Same old 405 Post not allowed error
am 19.01.2007 02:46:42 von Mark Diggory
Hello,
I've been doing my research and can't find a solution for this issue,
we have IP based virtual hosts with the following
directives (which we really need) and are getting the 405 Post not
allowed error. The issue does not seem to be addressed again for 3
years now. Is there a solution to this?
http://marc.theaimsgroup.com/?l=apache-modssl&m=104857625910 336&w=2
Here is my current configuration:
Gentoo: 1.12.6
mod_ssl: 2.8.25-r10
apache: 2.0.58-r2
mod_jk: 1.2.19
tomcat: 5.5.20-r7
Thanks in advance for any advice,
Mark R. Diggory
~~~~~~~~~~~~~
DSpace Systems Manager
MIT Libraries, Systems and Technology Services
Massachusetts Institute of Technology
____________________________________________________________ __________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List modssl-users@modssl.org
Automated List Manager majordomo@modssl.org
Re: Same old 405 Post not allowed error
am 19.01.2007 03:10:18 von Dave Paris
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Mark,
a) you never added the contents of your directive (i.e. "with
the following directives..")
b) you don't specify *why* you need these, particularly given that
you're using IP-based virtual hosts. (i.e. "(which we really need)")
Without this information, it's impossible to answer your question and I
highly suspect that your solution lies with a minor reconfiguration.
Kind Regards,
- -dsp
Mark Diggory wrote:
> Hello,
>
> I've been doing my research and can't find a solution for this issue, we
> have IP based virtual hosts with the following directives
> (which we really need) and are getting the 405 Post not allowed error.
> The issue does not seem to be addressed again for 3 years now. Is there
> a solution to this?
>
> http://marc.theaimsgroup.com/?l=apache-modssl&m=104857625910 336&w=2
>
> Here is my current configuration:
>
> Gentoo: 1.12.6
> mod_ssl: 2.8.25-r10
> apache: 2.0.58-r2
> mod_jk: 1.2.19
> tomcat: 5.5.20-r7
>
> Thanks in advance for any advice,
>
> Mark R. Diggory
> ~~~~~~~~~~~~~
> DSpace Systems Manager
> MIT Libraries, Systems and Technology Services
> Massachusetts Institute of Technology
>
>
> ____________________________________________________________ __________
> Apache Interface to OpenSSL (mod_ssl) www.modssl.org
> User Support Mailing List modssl-users@modssl.org
> Automated List Manager majordomo@modssl.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)
iD8DBQFFsCiIKmNPF3QynfQRAomwAJ4pPBcfzWeeD93Q+YedPX8YV6ARMACf W4EZ
7277LvxtQRhQC8QzxBrE6h8=
=Eqmr
-----END PGP SIGNATURE-----
____________________________________________________________ __________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List modssl-users@modssl.org
Automated List Manager majordomo@modssl.org
Re: Same old 405 Post not allowed error
am 19.01.2007 03:32:24 von Mark Diggory
Yes, I did mean to have that included. -thanks.
> # SSL Engine Switch:
> SSLEngine on
>
> # Server Certificate:
> SSLCertificateFile /etc/apache2/ssl/.....
>
> # Server Private Key:
> SSLCertificateKeyFile /etc/apache2/ssl/.....
>
> # Certificate Authority (CA):
> SSLCACertificateFile /etc/apache2/ssl/....
>
>
> # Force X.509 certificates to be used for this location
>
> Allow from all
> Order allow,deny
> SSLVerifyClient optional
> SSLVerifyDepth 1
> SSLOptions +StdEnvVars +ExportCertData +OptRenegotiate
>
>
> # SSL Protocol Adjustments:
> SetEnvIf User-Agent ".*MSIE.*" nokeepalive ssl-unclean-
> shutdown downgrade-1.0 force-response-1.0
I've tried commenting out the and placing the SSL
directives at the VirtualHost level, this seems to work fine, but I
can't have VerifyClient across the entire site due to complaints from
users about Certificate challenges in I.E. etc.
thanks again,
Mark
On Jan 18, 2007, at 9:10 PM, Dave Paris wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi Mark,
>
> a) you never added the contents of your directive (i.e.
> "with
> the following directives..")
> b) you don't specify *why* you need these, particularly given that
> you're using IP-based virtual hosts. (i.e. "(which we really need)")
>
> Without this information, it's impossible to answer your question
> and I
> highly suspect that your solution lies with a minor reconfiguration.
>
> Kind Regards,
> - -dsp
>
> Mark Diggory wrote:
>> Hello,
>>
>> I've been doing my research and can't find a solution for this
>> issue, we
>> have IP based virtual hosts with the following directives
>> (which we really need) and are getting the 405 Post not allowed
>> error.
>> The issue does not seem to be addressed again for 3 years now. Is
>> there
>> a solution to this?
>>
>> http://marc.theaimsgroup.com/?l=apache-modssl&m=104857625910 336&w=2
>>
>> Here is my current configuration:
>>
>> Gentoo: 1.12.6
>> mod_ssl: 2.8.25-r10
>> apache: 2.0.58-r2
>> mod_jk: 1.2.19
>> tomcat: 5.5.20-r7
>>
>> Thanks in advance for any advice,
>>
>> Mark R. Diggory
>> ~~~~~~~~~~~~~
>> DSpace Systems Manager
>> MIT Libraries, Systems and Technology Services
>> Massachusetts Institute of Technology
>>
>>
>> ____________________________________________________________ _________
>> _
>> Apache Interface to OpenSSL (mod_ssl)
>> www.modssl.org
>> User Support Mailing List modssl-
>> users@modssl.org
>> Automated List Manager
>> majordomo@modssl.org
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.1 (Darwin)
>
> iD8DBQFFsCiIKmNPF3QynfQRAomwAJ4pPBcfzWeeD93Q+YedPX8YV6ARMACf W4EZ
> 7277LvxtQRhQC8QzxBrE6h8=
> =Eqmr
> -----END PGP SIGNATURE-----
> ____________________________________________________________ __________
> Apache Interface to OpenSSL (mod_ssl) www.modssl.org
> User Support Mailing List modssl-users@modssl.org
> Automated List Manager majordomo@modssl.org
Mark R. Diggory
~~~~~~~~~~~~~
DSpace Systems Manager
MIT Libraries, Systems and Technology Services
Massachusetts Institute of Technology
____________________________________________________________ __________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List modssl-users@modssl.org
Automated List Manager majordomo@modssl.org