Skip to main content
Inspiring
November 6, 2008
Question

After processing a form??

  • November 6, 2008
  • 2 replies
  • 253 views
Currently when users fill out forms on our site, the forms are send to a
/CF directory for processing. I'd like to then, at the end of the processing
redirect them to another page to display the results, but am curious if its
possible to redirect them to a .htm/.html page and still display some information
from the dynamic CF side of things.

So, if I redirect them to a .htm page, can I include CF query results?

Hopefully this makes sense. I am familar with the <cflocation> tag to redirect,
but I guess my question goes to more of the use of query results on the .htm/html
page.....

Has anyone done anything like this????


    This topic has been closed for replies.

    2 replies

    Inspiring
    November 6, 2008
    Why is cf vs html even relevent?
    Inspiring
    November 6, 2008
    steve grosz wrote:
    > my question goes to more of the use of query
    > results on the .htm/html page.....


    Technically No. There are ways to fake it, but strictly speaking an
    .htm/html page is not dynamic.

    It goes to the relationship between the web server (IIS|Apache|etc) and
    the application server (ColdFusion|ASP|.NET|etc).

    The web server gets a request for a resource. *IF* the resource is
    associated with an application server, i.e, ends in .cfm or .aspx, the
    web server hands this off to the application server to do its job.

    If the resource is *NOT* associated with an application server, i.e.
    ends in .htm or .html or .js or .css, then the web server just fetches
    the specified file and delivers it to the client that requested it. As
    is, no processing, no changes.

    There are two ways you can change this process flow.

    One. You can associate the desired file type with the application
    server. I.E. you can configure your web server to hand all .html files
    to the application server for processing. If this is done then
    ColdFusion would get the .html file and process any CFML it might find
    in it before sending it to back to the web server for delivery to the
    requesting client.

    Two. You can have the CFML that processes the form dynamically build the
    content and write it to the .htm|.html file before you relocate to it
    with the <cflocation...> tag.
    Inspiring
    November 6, 2008
    Hello Ian,

    I was thinking about your option 2 when I posted this. The only question
    I had is what happens if 2 people are doing that at the same time, or close
    to it????

    Do you have any examples of how to build it dynamically?


    Thanks!
    Steve

    > steve grosz wrote:
    >
    >> my question goes to more of the use of query results on the .htm/html
    >> page.....
    >>
    > Technically No. There are ways to fake it, but strictly speaking an
    > .htm/html page is not dynamic.
    >
    > It goes to the relationship between the web server (IIS|Apache|etc)
    > and the application server (ColdFusion|ASP|.NET|etc).
    >
    > The web server gets a request for a resource. *IF* the resource is
    > associated with an application server, i.e, ends in .cfm or .aspx, the
    > web server hands this off to the application server to do its job.
    >
    > If the resource is *NOT* associated with an application server, i.e.
    > ends in .htm or .html or .js or .css, then the web server just fetches
    > the specified file and delivers it to the client that requested it.
    > As is, no processing, no changes.
    >
    > There are two ways you can change this process flow.
    >
    > One. You can associate the desired file type with the application
    > server. I.E. you can configure your web server to hand all .html
    > files to the application server for processing. If this is done then
    > ColdFusion would get the .html file and process any CFML it might find
    > in it before sending it to back to the web server for delivery to the
    > requesting client.
    >
    > Two. You can have the CFML that processes the form dynamically build
    > the content and write it to the .htm|.html file before you relocate to
    > it with the <cflocation...> tag.
    >