MACROMEDIA COLFUSION MX 7-CFML Guía de usuario Pagina 53

  • Descarga
  • Añadir a mis manuales
  • Imprimir
  • Pagina
    / 56
  • Tabla de contenidos
  • MARCADORES
  • Valorado. / 5. Basado en revisión del cliente
Vista de pagina 52
BlueDragon 7.1: Deploying CFML on ASP.NET and the Microsoft .NET Framework 48
port discussion in section 1.5 for contact information. We want to hear from you in order to eva-
luate and attempt to resolve your challenge.
8.4 .NET Security Issues that May Affect CFML Processing
The .NET Framework has implemented tighter security mechanisms to avoid common problems
in web application development. Some more global settings were discussed in section 2.1.2.
There are also several more localized security mechanisms that are specific to .NET. As is often
the case, the tighter security can also be a hindrance if you do not expect and understand it. The
following sections describe some pertinent .NET security features.
8.4.1 Problems Processing CFDIRECTORY, CFFILE Actions
There can be challenges using certain CFML tags such as CFDIRECTORY and CFFILE, which
can be used to create or modify directories and files on the server. By default, the user under
which ASP.NET runs has quite limited permissions. This is a security precaution. It isn’t even
authorized to create or modify directories within the web docroot.
If a directory is not modified to specifically permit read access to the user under which ASP.NET
runs, an attempt to use CFFILE action="read" will give the CFML Runtime error, File
Specified No Longer Exists
, not a .NET error; and if it’s not modified to permit the List
Folder Contents
access, then an attempt to use CFDIRECTORY ACTION="list" will get
Error Getting Directory List
In order to enable tags that do perform such actions, you must grant authority to the account un-
der which ASP.NET is running. The default on Windows 2000 and Windows XP is a user called
ASPNET. On Windows 2003, the account is NETWORK SERVICE.
The process of granting authority for a given file or directory may vary depending on the specific
version of Windows that you’re running. In Windows XP, for instance, you may need to perform
a preliminary step in order to even control the security for a given directory. By default there is
no visible means to modify the security settings for a file or directory. You must use Windows
Explorer, to choose its Tools>Folder Options>View>Advanced Settings in order to
uncheck the option Use Simple File Sharing.
Having enabled that option, you will then see a Security tab when you select the properties for
a file or directory (right-click it and choose Properties). To add new permissions, click the
available Add button, then Advanced, then Find Now. Find and select the appropriate user
(ASPNET or NETWORK SERVICE, as discussed above), then select OK, then OK again. Finally,
with that user selected, choose the appropriate options (Modify, Read, Full Control) as
you deem appropriate for the action desired.
8.4.1.1 Creation of Fusebox Parsed Files May Fail
Those executing a Fusebox 4 application may experience an error for this same reason, where the
attempt to write a “parsed” file for a given request (as generated by the Fusebox framework) may
fail. The error may say:
An Error during write of Parsed File or Parsing Directory not
found.
Vista de pagina 52
1 2 ... 48 49 50 51 52 53 54 55 56

Comentarios a estos manuales

Sin comentarios