Context Bug?

[John Copsey]

Not sure if this is a bug in the way mod_cfml creates contexts or if this is a problem with tomcat contexts in general, but installing new instance of lucee (5.2.5) on a new ec2 box i can’t access any site’s on IIS using http://127.0.0.1:/index.cfm as all i ever get is the lucee welcome page instead of my own sites index.cfm which i think is caused by mod_cfml trying to setup a duplicate context for 127.0.0.1 (which already exists for the welcome page) relevant logs below.

is this something that can be fixed or is it not possible?

[mod_cfml] Counters have been reset (maxContexts, timeBetweenContexts)
[mod_cfml] host [127.0.0.1:88] contains ':'. New value => 127.0.0.1
[mod_cfml] Decoded Request URI => /index.cfm
[mod_cfml] QueryString => null
[mod_cfml] DocRoot Value => C:\blah\
[mod_cfml] Webserver main Host => w3svc2
[mod_cfml] Alias Value => 127.0.0.1
[mod_cfml] FATAL: Host [127.0.0.1] already exists.

i actually originally though it was a bug in the IIS connector on server 2016 and reported it here as others had reported similar issues on the lucee forum with using lucee on server 2016 but given the logs above it seems likely it’s being cause by mod_cfml.

​

This message is private and confidential and for the exclusive use of the intended recipient(s). If you receive this email in error, please notify the sender immediately and delete all copies from your system. If you are not the intended recipient disclosure, distribution, copying or use of this communication is strictly prohibited. Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of IDG UK. Clients and suppliers can view our full terms and conditions at www.idg.co.uk/terms-and-conditions/

IDG Communications Ltd. Company Reg No: 1197840. Registered in England and Wales.

[John Copsey]

For some reason the 127.0.0.1 port part was removed from the my message above so just to clarify this seems to effect any site using a port binding so for example if i was using http://127.0.0.1:88/index.cfm although i guess even if you used the default site in iis you wouldn't be able to either.

[Paul Klinkenberg]

Hi John,

What you are seeing is not a bug, but a limitation to what Mod_cfml can do. Sites can not be added to Tomcat based on a different port number. Instead, different host names have to be used.

Tomcat has a default site set up at 127.0.0.1, which is the one you are seeing. This default site has the mod_cfml connector installed, to check if a new site needs to be added. But mod_cfml sees the incoming url is "http://127.0.0.1", and hey, there already is a site in tomcat for that, so it exits.

It strips away the port number "88", as you saw in your log. That is because Tomcat does not have the ability to host sites based on port number.

The way to work around this, is to use specific hostnames for the sites you are adding.

First add a hostname to your Hosts file, e.g. "127.0.0.1 www.mysite.local"

Then add that hostname to the site in IIS.

That way, everything should work fine.

Hope that helps, kind regards,

Paul Klinkenberg

Op 9 jul. 2018, om 13:38 heeft John Copsey <john_...@idg.co.uk> het volgende geschreven:

Not sure if this is a bug in the way mod_cfml creates contexts or if this is a problem with tomcat contexts in general, but installing new instance of lucee (5.2.5) on a new ec2 box i can’t access any site’ on IIS using http://127.0.0.1:/index.cfm as all i ever get is the lucee welcome page instead of my own sites index.cfm which i think is caused by mod_cfml trying to setup a duplicate context for 127.0.0.1 (which already exists for the welcome page) relevant logs below.

is this something that can be fixed or is it not possible?

[mod_cfml] Counters have been reset (maxContexts, timeBetweenContexts)
[mod_cfml] host [127.0.0.1:88] contains ':'. New value => 127.0.0.1
[mod_cfml] Decoded Request URI => /index.cfm
[mod_cfml] QueryString => null
[mod_cfml] DocRoot Value => C:\blah\
[mod_cfml] Webserver main Host => w3svc2
[mod_cfml] Alias Value => 127.0.0.1
[mod_cfml] FATAL: Host [127.0.0.1] already exists.

i actually originally though it was a bug in the IIS connector on server 2016 and reported it here as others had reported similar issues on the lucee forum with using lucee on server 2016 but given the logs above it seems likely it’s being cause by mod_cfml.

​

This message is private and confidential and for the exclusive use of the intended recipient(s). If you receive this email in error, please notify the sender immediately and delete all copies from your system. If you are not the intended recipient disclosure, distribution, copying or use of this communication is strictly prohibited. Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of IDG UK. Clients and suppliers can view our full terms and conditions at www.idg.co.uk/terms-and-conditions/

IDG Communications Ltd. Company Reg No: 1197840. Registered in England and Wales.

--
You received this message because you are subscribed to the Google Groups "mod_cfml" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mod_cfml+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.