tracker issue : CF-3336106

select a category, or use search below
(searches all categories and all time range)
Title:

[ANeff] ER for: Add .htm/.html to cfusion\lib\neo-cron

| View in Tracker

Status/Resolution/Reason: Closed/Withdrawn/AsDesigned

Reporter/Name(from Bugbase): Aaron Neff / Aaron Neff (Aaron Neff)

Created: 09/24/2012

Components: Scheduler

Versions: 10.0

Failure Type: Enhancement Request

Found In Build/Fixed In Build: Final /

Priority/Frequency: Trivial / Unknown

Locale/System: English / Platforms All

Vote Count: 2

Currently, cfschedule only supports .txt and .log as cfschedule file extensions. This is not documented in the cfschedule doc (see #3335502). The only documentation of this is actually misplaced in the description for the "overwrite" scheduled task option in the Server Settings doc. (see #3335503).

I've seen two people in the last week caught off guard by .htm & .html not being supported by default.  Users have scheduled tasks which store HTML output.

This ER is for CF to include .htm/.html in cfusion\lib\neo-cron xml by default.

----------------------------- Additional Watson Details -----------------------------

Watson Bug ID:	3336106

External Customer Info:
External Company:  
External Customer Name: itisdesign
External Customer Email:

Attachments:

Comments:

Yeah, I encountered this as well. The reasoning was that it was a potential security breach to have a browsable file extension on the log file. I contended that that was not ColdFusion's concern, that was *my* concern, and should be left up to me. Which fell on deaf ears. I stand by what I said, and this should be remedied. -- Adam
Vote by External U.
17974 | September 25, 2012 12:41:31 AM GMT
Given this is apparently a change from CF9 (and earlier) behaviour, I'd class this as a bug, not as a feature request, and indeed is a backwards compat issue. -- Adam
Comment by External U.
17970 | September 25, 2012 12:44:56 AM GMT
I agree with the Adam and Aaron on this. I capture scheduled task output to .htm files with CF9 (these files are not placed inside of any websites, so they can't be browsed by website visitors). I use CFDUMP tags to output content of certain variables during processing, which significantly aids in troubleshooting problems. By making the extension of captured output .htm, I can open the C:\ColdFusion10\cfusion\logs folder and double-click on these files to view their contents when needed. Being restricted to .log or .txt makes it harder to view these in a browser.
Vote by External U.
17975 | September 25, 2012 09:20:01 AM GMT
Hi Adam, That's a good point. And I think if CF is going to break backward-compat by changing a setting, then it should probably permit the changed setting to be managed via CF Admin. Users should be able to re-enable backward compat easily via CF Admin, rather than making undocumented or improperly documented (both are the case in this situation) changes to CF's internal files. Thanks, -Aaron
Comment by External U.
17971 | October 03, 2012 07:56:35 PM GMT
The document of course needs to be changed. We should give an option to users to change the allowed extensions from the admin. However, we should not add .htm and .html extensions by default.
Comment by Rupesh K.
17972 | October 04, 2012 12:00:29 AM GMT
This is intentional implementation keeping security issues in mind. Anyways admins will always have a way of changing these values by directly editing neo-cron.xml
Comment by Uday O.
17973 | October 01, 2013 04:42:08 AM GMT