Closed (fixed)
Project:
JS Callback Handler
Version:
7.x-1.0-beta2
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
27 Dec 2012 at 15:58 UTC
Updated:
17 Jan 2013 at 14:20 UTC
hey
does it support other webserver?
If no, it would be great to support Nginx webserver.
We are using this for drupal as webhosting
https://github.com/omega8cc/nginx-for-drupal
http://drupal.org/project/issues/barracuda
http://drupal.org/project/issues/octopus
Comments
Comment #1
doitDave commentedI thought about this as well last week, but there is IMO a simple reason to not treat this as an option for this module: NGINX is not even supported by core, so there is no default "htaccess" you can base on or modify. Also there are few approaches to make Drupal work with nginx anyway.
(However, I would actually appreciate Drupal supporting more than Apache environments officially. But that is beyond my power.)
My honest opinion: Closed, won't fix, but I'll leave it open in kind I'm wrong with that.
Inb4: Same for IIS.
Comment #2
michielnugter commentedI see no reason why it shouldn't work on any other server that Drupal also runs on. The only thing is that you need to tell the server how to rewrite the path if you want to use clean urls.
I did a convert of the htaccess lines and came up with the following:
Can you verify this is working with nginx bennos?
Comment #3
michielnugter commentedComment #4
bennos commentedwill test it in a local dev enviroment.
also created a feature request in the barracude queue.
http://drupal.org/node/1876418
Comment #5
omega8cc commentedBOA will require an exception for
/js.phprequests, but in general, the correct method to support it is via location directive, and to avoid searching for other regex based locations and make it faster, it is enclosed in a literal match based, parent location.Comment #6
michielnugter commentedVery cool to see this module supported in barracuda! Thanks for this. I already updated the project page and I'll update the requirments check and configuration page to check for apache.
Is it possible to recognize ngnix server in a _SERVER variable?
Comment #7
omega8cc commentedYes, normally it is possible to detect nginx via standard
_SERVER["SERVER_SOFTWARE"]variable, however we have forced it in BOA to use fakeApacheSolarisvalue, just to satisfy some modules which refuse to work if they don't detect Apache. Not sure if this complicates things?Comment #8
michielnugter commentedHmm ok, that makes it a bit more difficult.
Can I recognize it any other way? Maybe by a file being present in the root, like an alternative to .htaccess?
Comment #9
omega8cc commentedThe problem is that there is nothing really Nginx specific to rely on, besides its real
_SERVER["SERVER_SOFTWARE"]name, and the .htaccess file is present to avoid false alarms from Boost and others, even if it is never used. Not sure how to make the module aware that it is in fact Nginx behind ApacheSolaris, and not break things for modules assuming there is just one web server in the world :/Comment #10
bennos commented@michielnugter
You can detect Apache and BOA (via ApacheSolaris). Implemting an autodetection would be the best. For any other webserver or custom nginx setup, just add a Checkbox "Custom" or if the autodetection does not match, and display a short summary what to do or a link to the readme.txt.
Comment #11
michielnugter commentedI added a select box to set the server software. This only makes sure the .htaccess check is only performed when using Apache.
I also revised the installation guide in the readme to reflect the changes.