Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Inside my 404 handler, I added:</p> <pre><code>&lt;cfheader statuscode="404" statustext="Not Found"&gt; &lt;cfheader name="Connection" value="Close"&gt; &lt;!--- this is the fix! ---&gt; </code></pre> <p>Closing the connection seems to work for some reason.</p> <p>And to output the page, I'm doing:</p> <pre><code>&lt;cfcontent reset="Yes" type="text/html"&gt; &lt;cfheader name="Content-Length" value="#Len(fullpage)#"&gt; &lt;cfoutput&gt;#fullpage#&lt;/cfoutput&gt; </code></pre> <p>... where the variable fullpage is the content of the 404 handler.</p> <p>Now I can now consistently return both a 404 status code error AND the entire contents of my error page. However, when a non-ColdFusion page is requested, the CGI values are not correct. Prior to CF10, I could get the requested page by looking at the CGI parameters, specifically CGI.query_string, which used to look like: “404;<a href="http://www.example.com/some/file.html" rel="nofollow">http://www.example.com/some/file.html</a>” Now I’m getting: “404;<a href="http://www.example.com/jakarta/isapi_redirect.dll" rel="nofollow">http://www.example.com/jakarta/isapi_redirect.dll</a>”, which makes it impossible to get the requested page.</p> <p>However, the fact that I can now return an entire document makes this at least a partial workaround to the bug, which is still open (after over a year of CF10 being released)! For now, instead of trying to figure out what page was requested and looking at my sitemap, I'm simply outputting a standard "page not found" error.</p> <p>I should also mention that I'm using the same 404 handler in the onMissingTemplate method in Application.cfc. The requested page is passed into this method, which I then pass to my 404 handler in the Attribute scope, and I call my 404 handler as a cfmodule. So this is a complete solution when it's a ColdFusion page being requested, and only a partial solution when a non-CF page is requested (since we can't determine the requested file).</p>
    singulars
    1. This table or related slice is empty.
    1. POProblems handling 404 errors in ColdFusion 10 on Win2k8 R2 x64?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USRedtopia
    1. USRedtopia
    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. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COFor more information about the missing requested file name see this - [ColdFusion 10 + IIS: Non-existant URLs that are CFM files. Retrieving original URL after executing 404 page](http://stackoverflow.com/q/18694932/1636917)
      singulars
      1. PO
      1. USMiguel-F
    2. COI looked at that thread and it seems like the only workaround is to install the Ionic IIS Redirector as a 3rd party ISAPI app.
      singulars
      1. PO
      1. USRedtopia
    3. COI don't know if that is the only workaround but a couple of people have done that. Did you notice that they also entered a bug for this with Adobe. I am interested to see how they reply to that. If nothing else perhaps they can reply with their recommended configuration to retrieve the requested page. Vote for the bug if you haven't already - https://bugbase.adobe.com/index.cfm?event=bug&id=3630245.
      singulars
      1. PO
      1. USMiguel-F
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

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