Monday 15 August 2011

php - Custom header or query string when proxying request from Nginx to HHVM? -


I am using the directions in the following post as a guideline using Nginx as a proxy in front of HHVM :

Now that I have been able to successfully do it in two different ways, it is forwarding information to the original URI, as follows:

  location ~ .php $ {proxy_set_header Nginx-Uri $ myuri; Proxy_pass http://127.0.0.1:8064/index.php?orig_uri=$myuri; }   

Now I can access the custom header 'NGN-Uri' using getallheaders () or get the same information via $ _SERVER ['QUERY_STRING']. But is one way better for another? I had some doubt as to whether HHVM would be supported, because of this, PHP is already being supported for APK modules, while HHVM is its own server, but HHVM still works similarly, So apparently there is no idea.

In advance thank you

Both will work for the near future.

I personally dislike Magic Globals and prefer the function, but this is only personal preference. I getalheaders () should work on all transport methods, even we fastcgi , Modhhvm, or even after implementing our own libevent server. If we can analyze your code and never use a super super global, then we have to improve it, we do not have to populate it.

No comments:

Post a Comment