Mark, going back to your original problem. I am not sure if you have IPv4
IPv6 installed, but I just double checked that the local loop backs
addresse for IpV4 V6 are in my IP debugging list. Can you try adding them
both in and restarting ColdFusion and lets us know how you go.
Regards,
Andrew
You're right Dave you may need to re-read the threads again, because I am
well aware of the error status pages. I was mainly talking to Charles about
Friendly Error messages when you dropped by, if you are confused by that,
this is not my problem.
Regards,
Andrew Scott
WebSite:
by default IIS will display a 500 server error if it gets back a CF error
page as it doesn't know what to do with it as it doesn't send a valid error
code that matches any IIS errors.
In order to see the REAL cf error you have to turn on detailed error
messages in IIS, or you have to create a
You're right Dave you may need to re-read the threads again, because I am
well aware of the error status pages. I was mainly talking to Charles about
Friendly Error messages when you dropped by, if you are confused by that,
this is not my problem.
You wrote an email. I responded to that
Whatever Dave, like I said this option is for ASP only.
Here is a support article that a quick Google search dug up, if you can
provide where in IIS you make this change I will eat my words.
https://support.microsoft.com/en-us/kb/294807?wa=wsignin1.0
I'm not sure what posting a page about
My own personal, and albeit completely anecdotal, experience bears out what
Russ has written. By default you get the crappy 500 error, which the first
time I encountered it kept me running in circles for a while because I
didn't think it was coming from CF.
Hopefully the OP is at least being
the only person arguing here is you, you seem very insistent on getting the
last word and one-upping everyone today.
All I have done is assert a fact I know to be true.
On Mon, Apr 6, 2015 at 8:52 PM, Andrew Scott andr...@andyscott.id.au
wrote:
Russ,
*sigh* I think you're arguing with the
clealry I do know better than you, I suggest you take off your arrogamce
hat for a while and actually try it with a clean install of IIS and you
will find out that I am correct and that CF errors are not displayed by
default, just a 500 server error.
On Mon, Apr 6, 2015 at 8:35 PM, Andrew
sorry but you are wrong, as a hosting provider I deal with this all the
time on many many servers.
what I said below is correct.
On Mon, Apr 6, 2015 at 8:23 PM, Andrew Scott andr...@andyscott.id.au
wrote:
Russ,
By default IIS is set to either send Detailed if local or Custom if remote,
if
Russ,
By default IIS is set to either send Detailed if local or Custom if remote,
if one is changing this setting on a remote server it is likely to be a
production server and should not be be touched. At least this is the way I
read that, but again you don't need to touch any IIS setting when
Russ,
*sigh* I think you're arguing with the wrong guy. Yes, that is what
happens. Under a default install of IIS, the setting for the error pages is
as described in the picture in the last link I sent. There is no denying
that is the default setting, then on top of that I clearly stated that
ârotflmao, as a hosting provider you should know better.â
Regards,
Andrew Scott
WebSite: http://www.andyscott.id.au/
Google+: http://plus.google.com/113032480415921517411
On Tue, Apr 7, 2015 at 5:34 AM, Russ Michaels r...@michaels.me.uk wrote:
sorry but you are wrong, as a hosting
Not to mention the display friendly error messages in IIS, is for ASP!!
Regards,
Andrew Scott
WebSite: http://www.andyscott.id.au/
Google+: http://plus.google.com/113032480415921517411
On Mon, Apr 6, 2015 at 12:24 PM, Russ Michaels r...@michaels.me.uk wrote:
yes that is true, however debug
Andrew,
IIS will capture CF errors and display friendly error messages if it is set to.
The debugging output, however, should display regardless of this setting as,
as you stated, it is not an error. I would look at the source to see if the
output is being generated and simply being hidden
David,
I am very well aware after nearly 20 years of CF Development how it works,
IIS doesn't capture CF errors at all. It only displays what is sent to it,
in ColdFusion's case if it is not sending the status codes it usually ends
up with a blank page. You can make any adjustments to IIS you
I am very well aware after nearly 20 years of CF Development how it works,
IIS doesn't capture CF errors at all. It only displays what is sent to it,
in ColdFusion's case if it is not sending the status codes it usually ends
up with a blank page. You can make any adjustments to IIS you like
I guess my installs of IIS work, cause the only time I have to make any
changes is in CF where it says send HTTP status codes, nothing more and
nothing less.
Regards,
Andrew Scott
WebSite: http://www.andyscott.id.au/
Google+: http://plus.google.com/113032480415921517411
On Tue, Apr 7, 2015 at
Hi
We have one CF web server running CF11 and noticed that the CFTOKEN and CFID
cookies on that server have a long (51 char) string of random looking
characters before the actual CFID or CFOTKEN numeric value.
Ex: CFTOKEN = Z3epk1hxi861r0je68dw9xjrpf2oqa1vm0ygobljizhhw2d5gjh-22151980
Within
But Dave.
This in IIS
friendly error messages
Has nothing to do with ColdFusion output, nothing at all.
Regards,
Andrew Scott
WebSite: http://www.andyscott.id.au/
Google+: http://plus.google.com/113032480415921517411
On Tue, Apr 7, 2015 at 2:23 AM, Dave Watts dwa...@figleaf.com wrote:
I guess my installs of IIS work, cause the only time I have to make any
changes is in CF where it says send HTTP status codes, nothing more and
nothing less.
That's good for you! But there are many installs of IIS out there
besides your own, and those installs might be configured differently
I believe the issue here, is that when you have the status code option set in
ColdFusion, ColdFusion uses an H TTP status of 200, even for error pages.
If you don't have that option, ColdFusion sends out status codes of 500 or
whatever with there's an eeror. IIS does intercept those.
Forget
Charles it is neither here nor there. ColdFusion Robust Exceptions need
this setting to be enabled in ColdFusion, the display friendly error
messages is a browser option and is not something one has to touch anyway.
The other option in IIS is the setting of Custom ASP errors, there is no
other
This in IIS
friendly error messages
Has nothing to do with ColdFusion output, nothing at all.
No, but that's not what I responded to. Here's what I responded to,
specifically:
I am very well aware after nearly 20 years of CF Development how it
works, IIS doesn't capture CF errors at all.
Whatever Dave, like I said this option is for ASP only.
Here is a support article that a quick Google search dug up, if you can
provide where in IIS you make this change I will eat my words.
https://support.microsoft.com/en-us/kb/294807?wa=wsignin1.0
Regards,
Andrew Scott
WebSite:
24 matches
Mail list logo
