I have noticed a difference in the way MX8 handles Symbolic
Links within the template path directory.
Consider:
/opt/coldfusion/www/site1/Application.cfm
/opt/coldfusion/www/common/util.cfm
/opt/coldfusion/www/site1/common -> /opt/coldfusion/www/common (symbolic link)
When accessing http://127.0.0.1/site1/common/util.cfm, the resulting template path is /opt/coldfusion/www/common/util.cfm versus /opt/coldfusion/www/site1/common/util.cfm and Application.cfm is not included.
Creating the identical scenario in MX6 works as expected, where the template path is /opt/coldfusion/www/site1/common/util.cfm and Application.cfm is included.
Is there a configuration within CF or JRun that controls how Symbolic Links are handled? It really doesn't make sense that the application layer would negate an OS level configuration. Please help as this is a key component to our upgrade path from MX6 to MX8.
Thank you.
Consider:
/opt/coldfusion/www/site1/Application.cfm
/opt/coldfusion/www/common/util.cfm
/opt/coldfusion/www/site1/common -> /opt/coldfusion/www/common (symbolic link)
When accessing http://127.0.0.1/site1/common/util.cfm, the resulting template path is /opt/coldfusion/www/common/util.cfm versus /opt/coldfusion/www/site1/common/util.cfm and Application.cfm is not included.
Creating the identical scenario in MX6 works as expected, where the template path is /opt/coldfusion/www/site1/common/util.cfm and Application.cfm is included.
Is there a configuration within CF or JRun that controls how Symbolic Links are handled? It really doesn't make sense that the application layer would negate an OS level configuration. Please help as this is a key component to our upgrade path from MX6 to MX8.
Thank you.