New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Server 2016 / IIS 10 Supported #67
Comments
Also i've read about a permissions issue with some boncode files when install lucee on server 2016 here but i'm running the app pool as administrator so if there was a permissions issue that shouldn't be a problem in this case, although i'm not really clear what the poster did to fix their issue to be honest. |
Mostly looks good. Best, |
Look for a package |
The default connector installed with lucee doesn't seem to have that command and would 404 on non existent files but i installed the latest release to get the config list. When you say look for a package what do mean? i couldn't see anything in the boncode logs should i look in the windows event logs? I think i restarted IIS to get the connector to enable logging but i've restarted the box on this attempt just to be sure it all working ok as the server roles/features were fresh installs. Default Connector (/index.cfm?BonCodeConnectorVersion=true)
Newest Release (/index.cfm?BonCodeConnectorVersion=true)
Newest Release (/index.cfm?BonCodeConfigList=true)
|
i used wireshare to capture the request going to the ajp connector which clearly showed the correct header being set so started looking into the possibility the problem is being caused by mod_cfml which after enabling logging on it seems likely it is a bug in mod_cfml. Sorry for wasting you time, would it be worth adding a feature request to add the tomcat doc root header to the connector log? as not seeing it there was my main reason for thinking it was caused by the connector. Here's the log from mod_cfml for anyone else who come across the same behaviour.
|
You need to set the log level to 4
You should see the X-headers in special data package type (18).
If you do, all data is sent correctly and further investigation should take place on tomcat side.
Mod_cfml valve should then automatically determine the site context and return index.cfm.
If not, you can also setup the new site manually on tomcat as new context.
Bilal
|
Hi,
I'm not entirely sure if this is a bug with the connector or mod_cfml but looking at the connector logs it suggest it might be the connector.
I've installed lucee 5.2.5 with the global/wildcard configuration for the connector in a new aws ec2 windows 2016 machine and after creating a new site in iis i only ever see the lucee welcome page instead the new sites index.cfm which suggest that the context isn't be setup in tomcat and when i enable the connector logging i don't see "x-tomcat-docroot" header mentioned which makes me think this might be caused by the connector, relevant config and logs included below.
C:\Windows\BonCodeAJP13.settings
C:\Windows\Temp\BonCodeAJP13Connection_2_EC2AMAZ-RP875G7_20180706.log
As you can see from the logs the connector does have the "appl-physical-path" header which the correct path for the web root but doesn't have a "x-tomcat-docroot" header which my understanding is should be enabled with
<EnableHeaderDataSupport>True</EnableHeaderDataSupport>
and is used by mod_cfml to setup the site context in tomcat.I've also tried changing the settings file to include
<DocRoot>C:\blah</DocRoot>
to see if it would be included that way but it didn't help.The text was updated successfully, but these errors were encountered: