Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Friendly URL autodetect (pingFU) sometimes fails on initialisation

Description

Problem
----------------------------------
periodically pingFU fails to initialise correctly when an application is restarted. Not sure if this is a race condition or simply it times out waiting for it. Will also be a problem on secure servers that have restrictions on internal browsing. Currently the workaround is to add:

<cfset application.fc.factory.farFU.turnOn() />

to serverSpecificVarsAfterInit.cfm. This forces them on all the time.

Suggested Solution
----------------------------------
Make this an optional config item that can be enabled via the webtop. default is off.

Environment

None

Activity

Show:

Justin Carter January 27, 2014 at 7:54 AM

The two main reasons for friendly URLs failing to turn on are:

  • the server is under load during the application startup and the cfhttp call to /pingFU fails

  • the server is behind a firewall or proxy where it can't access itself via the public IP address to which the host headers are bound in the web server (perhaps requiring a password in the case of a proxy) so the cfhttp call to /pingFU fails

The config option is definitely the way forward for the sake of simplicity.

Geoff Bowers October 9, 2011 at 7:37 AM

The original suggestion in the ticket of a config option seems the best approach to me. The auto detection caper of everything is asking a bit much given the variety of environments farcry can find itself in. However, a standard config entry in General to activate Friendly URLs would work well.

Given that it will need to be turned on by folks once implemented, the change should go into 6.2.

Jeff Coughlin October 9, 2011 at 6:49 AM

Problem still exists. I have to use the workaround for every one of my clients (at least for p600.

I haven't used the latest p610 or trunk lately in production, but I don't believe it works in either version in my dev environments.

Jason Barnes October 9, 2011 at 12:51 AM

has not been resolved yet. Workaround is still the only guaranteed way to have FU's turned on

Matthew Bryant October 8, 2011 at 8:43 PM

I believe this has been sorted. Can this be closed?

Fixed

Details

Assignee

Reporter

Components

Fix versions

Affects versions

Priority

Parent

Created July 17, 2009 at 3:35 AM
Updated February 25, 2018 at 11:02 PM
Resolved February 25, 2018 at 11:02 PM