php-java-bridge-users Mailing List for PHP/Java Bridge

On Fri, Aug 6, 2010 at 5:33 AM, Mingfai <min...@gm...> wrote:

> hi,
>
> *Problem*
> I noticed a difference the $_SERVER['REQUEST_URI'] in PHP between a native
> php environment and in Java Bridge. In my test, I have a /test/index.php
> with the following line:
>   <?php echo $_SERVER['REQUEST_URI']?>
>
>
>

Other than REQUEST_URI, I notice HTTP_POST also caused a problem. The
current JavaBridge set the HTTP_POST with:
 env.environment.put("HTTP_HOST", env.environment.get("SERVER_NAME") + ":" +
env.environment.get("SERVER_PORT"));

For port 80, it includes the port number. The actually variable is sth like
acme.com:80 , but in Apache/Nginx, HTTP_HOST won't show the port number when
the port is 80.

Because Wordpress does url checking as a string, a slight different results
in a redirection. e.g. when the first request is http://acme.com/index.php,
wordpress' canonical.php redirect_canonical() will re-construct a
request_url with schema ("http://" or https://") . HTTP_HOST . REQUEST_URI.
The reconstructed url will becomes http://acme.com:80/index.php. As the
reconstructed uri doesn't match the request url which is
http://acme.com/index.php, it will make a redirect to the "correct" url
without the port number.  After redirected, JavaBridge appended the :80
again, and WP thinks it is wrong again and keep redirecting.

For this case, I think JavaBridge should match the standard way to set
variable like Apache and Nginx, i.e. not to include the port number for port
80 request.

With both REQUEST_URI and HTTP_HOST fixed, I'm able to run Wordpress with
JavaBridge.

regards,
mingfai

hi,

*Problem*
I noticed a difference the $_SERVER['REQUEST_URI'] in PHP between a native
php environment and in Java Bridge. In my test, I have a /test/index.php
with the following line:
  <?php echo $_SERVER['REQUEST_URI']?>

When I run Java bridge in Jetty, and used index.php as a welcome file in
web.xml, when I hit /test/, the REQUEST_URI is /test/index.php, i.e.
included the index file name.

But when run in Nginx, and used index.php as an index file, for an identical
request to /test/, the REQUEST_URI is /test/, i.e. without the index file
name.

This difference in behavior caused a trouble when running Wordpress as it is
too intelligent to try to redirect a link with /index.php to /, but after
the redirection, the servlet-Java-Bridge environment tell the PHP the new
request is from /index.php again and result as a dead loop.

Other than the modifying wordpress' source code to disable its "canonical
detection", I thought about a workaround to map the PHP CGI servlet to "/"
(or /* or whatever without .php at the end). It doesn't work and even if it
works, it will also map all static files like images or javascript files
(and favicon.ico!) to PHP.

*Solution*
Traced the code, I notice JavaBridge is using the following code to obtain
the request_uri in FastCGIServlet.java:
        env.requestUri = (String)
req.getAttribute("javax.servlet.include.request_uri");
        if (env.requestUri == null) env.requestUri = req.getRequestURI();

In my Jetty environment,
req.getAttribute("javax.servlet.include.request_uri") returns null,
however,  req.getAttribute("javax.servlet.forward.request_uri") will return
the correct uri before forwarding. (i.e. "/test/" instead of
"/test/index.php")

Both javax.servlet.include.request_uri and javax.servlet.forward.request_uri
are defined in the Servlet spec. For include, in Servlet spec 8.3.1, it is
stated that:

> javax.servlet.include.request_uri
> ...
> These attributes are accessible from the included servlet via the
> getAttribute method on the request object and their values must be equal to
> the request URI, context path, servlet path, path info, and query string of
> the included servlet, respectively. If the request is subsequently included,
> these attributes are replaced for that include.
>

For forward, in Servlet spec 8.4.2, it is stated that:


> javax.servlet.forward.request_uri
> ...
>
The values of these attributes must be equal to the return values of the
> HttpServletRequest methods getRequestURI, getContextPath, getServletPath,
> getPathInfo, getQueryString respectively, invoked on the request object
> passed to the *first servlet object* in the call chain that received the
> request from the client.
>

I'm not sure which one is supposed to be correct but the
javax.servlet.forward.request_uri attribute is said to be the request uri of
the first servlet object of a chain, that won't be modified by subsequent
servlet, and it gives a correct value in my test.

could JavaBridge make a change either to use the forward.request_uri or just
check both attributes? should i make a patch?

regards,
mingfai

On Thu, Aug 5, 2010 at 5:56 PM, <php...@li...
> wrote:

> > listening port of any started php-fpm pool only. I tried to make PHP-FPM
> to
> > listen to the default 9667, and the use_fast_cgi to disable autostart
> (used
> > "no") but it still doesn't work.
>
> "no" disables fastcgi altogether. Please set it to On.
>
>
> > I assume a started php-fpm is a fcgi server. and I want to make
> JavaBridge
> > use the fcgi server that i have started manually without trying to spawn
> any
> > fcgi connection/process. does it make sense?
>
> Yes, definitely. If you use PHP/Java Bridge version 6.2.1, remove
> php-cgi and then ask for some PHP page, the bridge will return an
> error message asking you to start a fastcgi server process.
>
>
> > do you know if php-fpm is a
> > kind of fcgi server that JavaBridge may support?
>
> Certainly. Just start it and configure the bridge to connect to its
> TCP port (Unix) or NamedPipe file (Windows). Or let the bridge decide
> which port or file to use and start the fastcgi process afterwards.
> ..
>
>
>
> Regards,
> Jost Bökemeier
>
>
thanks for your help. I'm about to get it work now. :-)

one of the things I did it wrong before is I have configured the php-fpm
pool with a chroot jail. the root path is changed by the chroot that
JavaBridge has no knowledge about.

regards,
mingfai

> listening port of any started php-fpm pool only. I tried to make PHP-FPM to
> listen to the default 9667, and the use_fast_cgi to disable autostart (used
> "no") but it still doesn't work.

"no" disables fastcgi altogether. Please set it to On.


> I assume a started php-fpm is a fcgi server. and I want to make JavaBridge
> use the fcgi server that i have started manually without trying to spawn any
> fcgi connection/process. does it make sense?

Yes, definitely. If you use PHP/Java Bridge version 6.2.1, remove
php-cgi and then ask for some PHP page, the bridge will return an
error message asking you to start a fastcgi server process.


> do you know if php-fpm is a
> kind of fcgi server that JavaBridge may support?

Certainly. Just start it and configure the bridge to connect to its
TCP port (Unix) or NamedPipe file (Windows). Or let the bridge decide
which port or file to use and start the fastcgi process afterwards.


> I'm trying to look at the source code to try to get this work. Now, I'm
> studying ContextLoaderListener and FastCGIServlet. Any pointer would be
> appreciated.

In version 6.2.1 the configuration has been moved from the
FastCGIServlet to the ContextLoaderListener, please see the NEWS file
for details: http://php-java-bridge.cvs.sourceforge.net/viewvc/php-java-bridge/php-java-bridge/NEWS?revision=1.87&view=markup


Regards,
Jost Bökemeier