Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
    1. COSimply blocking the whole `/CFIDE` directory is a bit of a sledgehammer/nut solution. The /CFIDE/administrator directory should be blocked or IP restricted, (and in doing that it's important to check /CFIDE/administrator/index.cfm isn't still accessible - IIS doesn't always apply directory blocks to files), and I think otherwise only `/CFIDE/scripts` and `/CFIDE/debug` actually _need_ web server access (the latter not publically) - but in general I think it's best for people to understand what/why they are blocking or not blocking, so an explanation along those lines would make a good answer.
      singulars
    2. COWe couldn't get anything working perfectly until our server administrator read Adam's solution. He implemented it and it worked perfectly. Neither he nor I are "CF Administrator configuration experts". He'll fix the security holes in the near future. For now, we are up and running. Thanks, Adam.
      singulars
    3. COTBH Peter, I disagree, but I see where you're coming from so we can just agree to disagree, perhaps. One shouldn't have debugging switched on in production, so the debug templates aren't needed. Equally, if if one is using CFFORM and other stuff that's deployed in the scripts dir, I'd home them elsewhere in production (and use CFAJAXIMPORT to point to the new location). It's just easier to not deploy the whole CFIDE dir at all. There's less scope for security-risk cock-ups then.
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload