[users@httpd] Problem Configuring httpd 2.4 to allow expired client certficates

2024-08-12 Thread J Harri
I am working on migrating an application to httpd 2.4 on AL2023.  The application uses client certificates, which will be expiring before they can all be rotated with new expirations. I am attempting to configure httpd 2.4 to continue requiring client certificates, but change the configuration t

Re: [users@httpd] mod_proxy health check custom header

2024-08-12 Thread Aaron Rosenzweig
Hi Eric thanks for digging into code to confirm what I was asking for isn't currently possible. Sounds like while it might be a reasonable enhancement, and somewhat easy to implement, it's not a slam dunk because it could have complications. Yes, you are right, by checking for a particular endpoin

Re: [users@httpd] mod_proxy health check custom header

2024-08-12 Thread Eric Covener
> Does anyone know how to configure the mod_proxy health check to use a custom > header? Or is it not possible currently? Thank you :-) Not a user but I checked the code and I don't think it's possible without an enhancement to mod_proxy_hcheck. The change would not be too bad though. https://g

[users@httpd] Re: mod_proxy health check custom header

2024-08-12 Thread Aaron Rosenzweig
Does anyone have advice for me regarding custom headers in mod_proxy health check? Thank you :-) On Wed, Aug 7, 2024 at 2:31 PM Aaron Rosenzweig wrote: > We have mod_proxy doing balancing and working great with the exception of > one thing, the health check. I'm talking about the heartbeat inter

Re: [users@httpd] error 500 on POST request

2024-08-12 Thread Andrija Vranić
thank you Aaron! On Mon, 12 Aug 2024 at 17:15, Aaron Rosenzweig wrote: > Hi Andrija. In your logs I don't see the 500 error so maybe you cut and > pasted the wrong log. But generally a 500 error means something fundamental > went wrong and it might have nothing to do with Apache. If generally yo

Re: [users@httpd] error 500 on POST request

2024-08-12 Thread Aaron Rosenzweig
Hi Andrija. In your logs I don't see the 500 error so maybe you cut and pasted the wrong log. But generally a 500 error means something fundamental went wrong and it might have nothing to do with Apache. If generally your python app works (Django is python under the covers right?) such as existing