LiveDocs Comments - coldfusion - 6 - CFML_Reference - Tags-pt154.htm

coldfusion/6/CFML_Reference/Tags-pt154.htm

qwerqwerqwe — 2004-10-18T08:54:36

If the site that you are CFHHTPing to is using SSL that has not been delivered by a trusted CA then the connection will fail. CF basicly gets the little confirmation box that says something like, are you sure you want to accpet this certificate? But CFMX cannot click yes there. I suppose this is alot like the Secure LDAP settings in CFMX where we will have to configure the cert in the cacerts cert store in order for it to be trusted. I have very rarely gotten this to work. There is very little information on the cacert store and how we can attain certs that will work once they are loaded into the cert store.

coldfusion/6/CFML_Reference/Tags-pt154.htm

2004-06-15T10:17:55

THese codes work in CF5 but not MX..anyone know why? Does MX still support query by name?

SELECT printer FROM info group by printer

coldfusion/6/CFML_Reference/Tags-pt154.htm

jrunrandy — 2003-10-24T09:17:36

ColdFusion MX 6.1 provides more flexibility with regard to delimiters. See http://livedocs.macromedia.com/coldfusion/6.1/htmldocs/tags-p58.htm#wp1632966 for details.

coldfusion/6/CFML_Reference/Tags-pt154.htm

2003-09-29T04:54:02

I want to put two enhancement
request for CFHTTP. Firstly, for
well-delimited files, the delimiters
should enclude pipe and space.
At least pipe (|) is one of the well known
delimeter. Secondly, it should be
able to deal with fixed-length files.
By using CFMX, we have lost the capability
to query the fixed length files, since it
does not suppot dynamic query any more.

coldfusion/6/CFML_Reference/Tags-pt154.htm

halL — 2003-09-24T07:23:35

The header attribute was added with ColdFusion MX 6.1.
This page documents ColdFusion MX 6.0. For 6.1 documentation, see http://livedocs.macromedia.com/coldfusion/6.1/.
The 6.1 version of this page also has a more complete description of the redirect attribute.

coldfusion/6/CFML_Reference/Tags-pt154.htm

csteinola — 2003-09-23T17:42:11

I have never understood just what the "redirect" attribute is supposed to do.
Near as I can tell, it's never worked (since 4.0). It never "redirects" anywhere (not in the common sense of the word), whether throwonerror = "yes" or not.

Can someone write clearer documentation for this attribute? Why, when, and how one would use it?

Ultimately, I'd like to be able to post data, and have the browser change location to the page I just posted to (much like a standard form post). I thought the new "HEADER" type for the HTTPPARAM tag would handle this (so you could pass a "Location" header)... but it doesn't seem to... or there's absolutely no documentation on how to make it so.

coldfusion/6/CFML_Reference/Tags-pt154.htm

jrunrandy — 2003-08-14T11:20:18

TheoPeter: I have entered this as enhancement request 53279.

coldfusion/6/CFML_Reference/Tags-pt154.htm

TheoPeters — 2003-08-12T15:11:41

Its just plain stupid that I have to use CFHTTP to turn a text file into a query object. I have to save text to a place that is visible to the Internet and then retrieve it through my own web server. This functionality should NEVER have been part of cfhttp. It should have been two different functions: 1) cfhttp can retrieve text from a web server. 2) queryobj = texttoquery( textstring) would convert ANY properly formatted text to a query.

coldfusion/6/CFML_Reference/Tags-pt154.htm

alinear — 2003-06-06T12:09:00

cfhttp.statuscode -- I believe 'throwonerror' has to be set to YES for this to attempt to work, and 'throwonerror' defaults to 'no'.

I am using a leased CFMX server on a shared server, so I cannot confirm this is not 'my fault'. But when I use cfhttp.statuscode in a catch like:

#CFHTTP.STATUSCODE#

#CFHTTP.FILECONTENT#

...I get an error something about 'statuscode' not being an object of cfhttp!

coldfusion/6/CFML_Reference/Tags-pt154.htm

phantem — 2003-05-19T18:03:00

Is there any way to use CFHTTP to grab a page that requires the existance of a cookie, but does not accept a POST request?

Since the cookies are sent in the header, shouldn't it be possible to submit them without having to use the POST method of CFHTTP?

coldfusion/6/CFML_Reference/Tags-pt154.htm

hlichtin — 2003-05-08T10:23:00

My response of today was to Jedimaster. The proxy issues are also known.

coldfusion/6/CFML_Reference/Tags-pt154.htm

hlichtin — 2003-05-08T10:20:00

This is a code bug and has been entered in the bug tracker.

coldfusion/6/CFML_Reference/Tags-pt154.htm

jedimaster — 2003-05-05T15:32:00

It seems as if redirect=yes is not the default. Someone reported an issue where his cfhttp did NOT redirect until he added redirect=yes. Can someone confirm this?

coldfusion/6/CFML_Reference/Tags-pt154.htm

saro28 — 2003-03-06T17:58:00

One of the Nightmare with CFHTTP is, it does not support proxy authentication. Would macromedia modify this tag to support Proxy authentication. Also SSL is not properly implemented.

coldfusion/6/CFML_Reference/Tags-pt154.htm

mesh — 2003-01-14T11:15:00

here is how to simply retrieve the contents of a web page:

#CFHTTP.fileContent#

coldfusion/6/CFML_Reference/Tags-pt154.htm

carehart@systemanage — 2003-01-02T08:15:00

I forgot to mention that there is a work-around until it's fixed. If you
know the number of columns in the file being read, you can just run a little
loop to create the column names automatically, as in:

Then use that created "colnames" value in the CFHTTP as
COLUMNS="#colnames#". Unfortunately, you have to know exactly how many
columns to use or a failure to specify the right amount will get an error
when CF tries to read the file and matches the number it finds against the
number of columns you generated. It would be nice if it just did itself as
it seems it's supposed to.

coldfusion/6/CFML_Reference/Tags-pt154.htm

carehart@systemanage — 2003-01-02T08:14:00

I forgot to add that there is a workaround one might use. If you know the number of columns in the file being read, you can just run a little loop to create the column names automatically, as in:

<cfset colnames="">

<cfloop from="1" to="7" index="i">

<cfset colnames = listappend(colnames,"column_"&i)>

</cfloop>

Then use that created "colnames" value in the CFHTTP as COLUMNS="#colnames#". Unfortunately, you have to know exactly how many columns to use or a failure to specify the right amount will get an error when CF tries to read the file and matches the number it finds against the number of columns you generated. It would be nice if it just did itself as it seems it's supposed to.

coldfusion/6/CFML_Reference/Tags-pt154.htm

carehart@systemanage — 2002-12-31T15:19:00

More unfortunate news on the new firstrowasheaders attribute. The docs above say that if it's set to "no" then:

- If the columns attribute is not specified: processes as data, and generates column names; for example, "column_1"

That would suggest that CF would create some column names automatically, which would be cool when one has a very large number of columns in the file being read. But I just tried it and simply got the error "The column name "1" is invalid." because that was the first column of data in the first row.

It's as if it's ignoring the firstrowasheaders="no" attribute. That attribute is indeed working if I add a COLUMNS attribute and give it column names, but again the point is that one shouldn't have to according to the docs.

coldfusion/6/CFML_Reference/Tags-pt154.htm

rnielsen — 2002-09-20T14:29:00

Here is another slight difference between CF5 and CFMX:

In ColdFusion MX, if the columns attribute is specified and firsrowasheaders = true (the default) there is an additional check for data integrity for all the rows of the retrieved file. CF5 will ignore the first row and perform no data checks against it but CFMX does. Hence MX will throw an 'Invalid Columns' or 'Invalid Number of Columns' exception if the first row of data file retrieved does not contain as many columns as specified in the columns attribute or contains invalid data.

coldfusion/6/CFML_Reference/Tags-pt154.htm

alex.lake — 2002-09-05T15:49:00

I found that the PORT attribute doesn't seem to work as advertised.

failed

but

worked

This represents a needless incompatibility with earlier versions of CF

coldfusion/6/CFML_Reference/Tags-pt154.htm

ctina — 2002-07-22T19:06:00

Update from Macromedia, CFHTTP tag, TYPE attribute = "xml":
this attribute specifies that the contentis XML. If method = "post", the xml is sent to the posting page as text in the http response header.

coldfusion/6/CFML_Reference/Tags-pt154.htm

ctina — 2002-07-22T14:24:00

Update from Macromedia, in response to fusebox_steve: I've entered your idea about an end tag for the HTMLHEAD tag into our enhancements suggestions list.

coldfusion/6/CFML_Reference/Tags-pt154.htm

rbils@amkor.com — 2002-07-16T03:41:00

In addition to the FIRSTROWASHEADERS attribute being broken in the release of CF MX, the documentation incorrectly states:

If FIRSTROWASHEADERS is No, and "If the columns attribute is specified: this attribute is not used"

This is not true. If the columns attribute is used, CF uses the list as the actual column headers for the query and treats the first row of the file as data. So, the attribute isn't ignored.

coldfusion/6/CFML_Reference/Tags-pt154.htm

fusebox_steve — 2002-07-01T22:20:00

should have an end tag. It's very annoying to have to escape double quotes.