CFFILE action=upload seeing application/pdf file as typetext/html

3 Message(s) by 2 Author(s) originally posted in cfml discussion

From: Adam Cameron

Date: Thursday, October 25, 2007

All <CFFILE action="upload

/uhp'lohd/ To transfer programs or data over a digital
	communications link from a smaller or peripheral "client"
	system to a larger or central "host" one.

	Opposite: {download}.

	[{Jargon File}]

	(1994-10-27)

"> does is move the file

<file system> An element of data storage in a {file system}.

	The history of computing is rich in varied kinds of files and
	{file systems}, whether ornate (e.g., {Macintosh file system}
	for a well-known case) or deficient (e.g., many simple
	pre-1980s file systems don't allow {directories}).

	However, the prototypical file has these characteristics:

	* It is a single sequence of bytes (but consider {Macintosh}
	{resource forks}).

	* It has a finite length, unlike, e.g. a {Unix} {device}.

	* It is stored in a {non-volatile storage} medium (but see
	{ramdrive}).

	* It exists (nominally) in a {directory}.

	* It has a name that it can be referred to by in file
	operations, possibly in combination with its {path}.

	Additionally, a file system may associate other information
	with a file, such as {permission} bits or other {file
	attributes}; timestamps for file creation, last revision, and
	last access; revision numbers (a` la VMS), and other kinds of
	{magic}.

	Compare: {document}.

	(1997-04-08)

from the web server's
temp dir to [wherever you specify]; it's more a "move" than an "upload".
And it's completely ignorant of MIME

<file format, multimedia> (MIME) A {standard} for multi-part,
	{multimedia} {electronic mail} messages and {World-Wide Web}
	{hypertext} documents on the {Internet}.  MIME provides the
	ability to transfer non-textual data, such as graphics,
	{audio} and fax.  It is defined in {RFC 2045}, {RFC 2046},
	{RFC 2047}, {RFC 2048}, {RFC 2049}, and {BCP0013}.  It uses
	{mimencode} to encode binary data into {base 64} using a
	subset of {ASCII}.

	{FAQ
	(http://www.cis.ohio-state.edu/hypertext/faq/usenet/mail/mime-faq/top.html)}.

	(1995-04-04)

type

<theory, programming> (Or "data type") A set of values from
	which a {variable}, {constant}, {function}, or other
	{expression} may take its value.  A type is a classification
	of data that tells the {compiler} or {interpreter} how the
	programmer intends to use it.  For example, the process and
	result of adding two variables differs greatly according to
	whether they are integers, floating point numbers, or strings.

	Types supported by most programming languages include
	{integers} (usually limited to some range so they will fit in
	one {word} of storage), {Booleans}, {floating point numbers},
	and characters.  {Strings} are also common, and are
	represented as {lists} of characters in some languages.

	If s and t are types, then so is s -> t, the type of
	{functions} from s to t; that is, give them a term of type s,
	functions of type s -> t will return a term of type t.

	Some types are {primitive} - built-in to the language, with no
	visible internal structure - e.g. Boolean; others are
	composite - constructed from one or more other types (of
	either kind) - e.g. {lists}, {arrays}, {structures}, {unions}.
	{Object-oriented programming} extends this with {classes}
	which encapsulate both the structure of a type and the
	operations that can be performed on it.

	Some languages provide {strong typing}, others allow {implicit
	type conversion} and/or {explicit type conversion}.

	(2003-12-22)

s (just like copying a file with
CTRl-C > CTRL-V in Windows

<operating system> See {Microsoft Windows}, {Windows NT}.

	(1997-11-23)

Explorer does not care either). The web server
handles the file upload from the client, not ColdFusion

<World-Wide Web, database, tool> {Allaire Corporation}'s
	commercial {database} application development tool that allows
	{databases} to have a {World-Wide Web} {interface}, so a
	database can be queried and updated using a {web browser}.

	The ColdFusion Server application runs on the {web server} and
	has access to a {database}.  ColdFusion files on the web
	server are {HTML} pages with additional ColdFusion commands to
	{query} or {update} the database, written in {CFML}.  When the
	page is requested by the user, the {web server} passes the
	page to the Cold Fusion application, which executes the {CFML}
	commands, places the results of the {CFML} commands in the
	{HTML} file, and returns the page to the {web server}.  The
	page returned to the {web server} is now an ordinary {HTML}
	file, and it is sent to the user.

	Examples of ColdFusion applications include order entry, event
	registration, catalogue search, directories, calendars, and
	interactive training.  ColdFusion applications are robust
	because all database interactions are encapsulated in a single
	industrial-strength {CGI} script.  The formatting and
	presentation can be modified and revised at any time (as
	opposed to having to edit and recompile {source code}).

	ColdFusion Server can connect with any database that supports
	{ODBC} or {OLE DB} or one that has a native database driver.
	Native database drivers are available for {Oracle} and
	{Sybase} databases.

	ColdFusion is available for {Windows}, {Solaris}, and {HP-UX}.
	A {development environment} for creating ColdFusion files,
	called ColdFusion Studio, is also available for {Windows}.

	Current version: MX(6), as of 2003-07-11.

	The {filename extension} for ColdFusion files is .cfm

	{Home (http://www.coldfusion.com/)}.

	(2003-07-27)

ColdFusion *never* has any direct
communications with the client-end of HTTP

<protocol> (HTTP) The {client-server} {TCP/IP} {protocol} used
	on the {World-Wide Web} for the exchange of {HTML} documents.
	It conventionally uses {port} 80.

	Current version: HTTP 1.1, defined in {RFC 2068}, as of May
	1997.

	See also {Uniform Resource Locator}.

	(1994-10-27)

communications; all it does is
talk (or listen) to the web server. Has anything changed on your web
server?

--
Adam

From: Henry K

Date: Thursday, October 25, 2007

I have a strange error

1. A discrepancy between a computed, observed, or measured
	value or condition and the true, specified, or theoretically
	correct value or condition.

	2. <programming> A mental mistake made by a programmer that
	may result in a program {fault}.

	3. (verb) What a program does when it stops as result of a
	programming error.

	(2000-03-28)

that has occurred within the last month or so, but I
have just encountered it today.

CFFILE no longer recognizes the correct mime type of files.

I'm running CFMX 7,0,1,116466 on Windows XP, Sun

JM 1.4.2_05-b04

Code that worked a month ago, if not later (like a week ago) is now returning:

The MIME type of the uploaded file "text/html" wasn't accepted by the server.

Only files of type "application/pdf" can be uploaded.
Verify that you are uploading a file of the appropriate type.

Am I missing something here? I do not think so, because code

<software> Instructions for a computer in some programming
	language, often {machine language}.  The word "code" is often
	used to distinguish instructions from {data} (e.g. "The code
	is marked 'read-only'") whereas "{software}" is used in
	contrast with "{hardware}" and may consist of more than just
	code.

	(2000-04-08)

that used to work
is no longer working.

I have attached some test code that will also result in error.
test file 1, fileUploadTest.cfm:

<form method="post" action="actFileUploadTest.cfm" name="uploadForm"
enctype="multipart/form-data">
<input name="pdfFileToUpload" type="file">
<br>
<input name="submit" type="submit" value="Upload File">
</form>

post action file:
<CFOUTPUT>
<CFSET destinationDir = "/path/to/an/upload/directory" >
<CFSET mimeAcceptList = "application/pdf">

<CFFILE action = "upload"
fileField = "pdfFileToUpload"
destination = "#destinationDir#"
accept = "#mimeAcceptList#"
nameConflict = "MakeUnique">
</CFOUTPUT>

From: Henry K

Date: Friday, October 26, 2007

Thanks for the response, Adam!

I checked with the admin, no changes were made to any of the servers, web or
cfmx, or to the jvm.

So I had to think about it and the only thing that changed was....my version

<programming> One of a sequence of copies of a program, each
	incorporating new modifications.  Each version is usually
	identified by a number, commonly of the form X.Y where X is
	the major version number and Y is the release number.
	Typically an increment in X (with Y reset to zero) signifies a
	substantial increase in the function of the program or a
	partial or total re-implementation, whereas Y increases each
	time the progam is changed in any way and re-released.

	Version numbers are useful so that the user can know if the
	program has changed ({bugs} have been fixed or new functions
	added) since he obtained his copy and the programmer can tell
	if a bug report relates to the current version.  It is thus
	always important to state the version when reporting bugs.
	Statements about compatibility between different software
	components should always say which versions they apply to.

	See {change management}.

	(1997-12-07)

of Firefox

<World-Wide Web> A complete {free}, {open-source} {web
	browser} from the {Mozilla Foundation} and therefore a true
	code descendent of {Netscape Navigator}.  The first non-{beta
	release} was in late 2004.

	{Firefox Home (http://www.mozilla.org/products/firefox)}.

	(2005-01-26)

!

After testing

<testing> The process of exercising a product to identify
	differences between expected and actual behaviour.  Typically
	testing is bottom-up: {unit testing} and {integration testing}
	by developers, {system testing} by testers, and {user
	acceptance testing} by users.

	{Test coverage} attempts to assess how complete a test has
	been.

	2. The second stage in a {generate and test} search
	{algorithm}.

	[{Jargon File}]

	(2003-09-24)

it out I think this is an issue with Firefox 2.0.0.8 (tested
only on windows), because the code works fine with IE 7, and on a version of FF
on OS X.

Firefox 2.0.0.8 is reporting files of type application/pdf as text/html.

Next Message: Can CF8 exist in an virtual machine environment