OK you guys:
We're upgrading from 2018 to 2023 and...
# cfml-generalp
phillipsenn
02/19/2024, 7:43 PMOK you guys:
We're upgrading from 2018 to 2023 and if I <cfset x=1/0> then I get a page full of error message. Wonderful.
But I only get it if I'm remoted into the server. I don't get it from my own browser.
I've turned on debugging and can see debugging info on my own browser, but <cfset x=1/0> produces a blank 500 internal server error when using my browser (but produces that nice full page of an error message if I'm remoted into the server).
Once again, they both produce debugging information if there is no error.
So I know it's not "debugging ip addresses"
👍 1
r
Ryan Albrecht
02/19/2024, 7:46 PMAre you using IIS?
p
phillipsenn
02/19/2024, 7:48 PMOh is that where the solution is? Yes I am on a windows server.
phillipsenn
02/19/2024, 7:49 PM"In the Features View, double-click on "Error Pages"."
r
Ryan Albrecht
02/19/2024, 7:49 PMPrehaps, I am assuming alot of things here but try adding this to you web.config
Ryan Albrecht
02/19/2024, 7:49 PM Copy code
<system.webServer>
<httpErrors existingResponse="Passthrough" />
</system.webServer>Ryan Albrecht
02/19/2024, 7:49 PMThat should forward the coldfusion error pages in the response instead of IIS
Ryan Albrecht
02/19/2024, 7:49 PMAssuming (again) thats what you want to achieve
p
phillipsenn
02/19/2024, 7:52 PMThank you! That did it!
👌 1
r
Ryan Albrecht
02/19/2024, 7:52 PMSweet
q
quetwo
02/20/2024, 1:19 PMBTW, showing raw error messages to end users is bad practice. It can reveal code to your end users and give attackers more insight into possible vulnerabilities.
☝️ 3
b
Brian
02/23/2024, 8:27 PM@phillipsenn Is that the only thing you did, add that setting to the web.config? Are you running IIS and the built-in Apache server or just the IIS?
2 Views