You're getting a 404 response. Are you sure you're pointing to the correct
location?
On Sun, Aug 1, 2021 at 7:26 PM JEA Holdings LLC
wrote:
> Test that method in beginning but was not working...
>
> Today test not working
>
> LOGS TODAY:
>
> On the MAIN root DIRECTORY
>
> > RewriteEngine On
Test that method in beginning but was not working...
Today test not working
LOGS TODAY:
On the MAIN root DIRECTORY
RewriteEngine On
RewriteRule .* - [env=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
After change httpd_access
192.168.22.217 - - [01/Aug/2021:18:35:56 -0400] "POST
/api/v1
> After many tests, I have concluded that what is happening is that header is
> not being sent to
> PHP-FPM since we use authorization and access, no response payload is being
> provided on POST with
> PHP-FPM (my findings).
>
> The app does header authentication via JWT and outside of the authe
Appreciate the assistance didn't want to post too many logs on my first
message...
-I tested on reverse NGINX proxy = DID not work
-I tested on NGINX with HTTP AND FastCGI = DID not work (same issue).
I will post the Apache httpd at the end but here is a flavor of working
and not working logs
The error log entries on the httpd and php-fpm side will be helpful to
continue troubleshooting.
A POST request is not typically a problem for this configuration.
On Thu, 29 Jul 2021 at 23:47, JEA Holdings LLC
wrote:
> Hello...
>
> Our project has moved to a new OS that needs PHP-FPM I got the
Hello...
Our project has moved to a new OS that needs PHP-FPM I got the httpd to
work sites are serving no problem via Unix Socket using FastCGI mod
ProxyPassMatch ^/(.*\.php(/.*)?)$
unix:/path/to/socket.sock|fcgi://localhost/path/to/your/documentroot/
+
Reverse with
# Note: The only
