Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cfprocessingdirective in the error handler page #33

Closed
GoogleCodeExporter opened this issue Jul 17, 2015 · 1 comment
Closed

cfprocessingdirective in the error handler page #33

GoogleCodeExporter opened this issue Jul 17, 2015 · 1 comment

Comments

@GoogleCodeExporter
Copy link


My Application.cfm :

----------------------------------------------
<cferror
    type="exception"
    template="error.cfm" />
----------------------------------------------


My error.cfm :

----------------------------------------------
<cfprocessingdirective pageencoding="utf-8">
Si le problème persiste, contactez-nous
----------------------------------------------


If I call directly the page error.cfm in my browser, I see 'Si le problème 
persiste, contactez-nous'

But if an exception is throw on OpenBD, I see : 'Si le probl�me persiste, 
contactez-nous'. So charset encoding seems to be bad..

All templates are created with cfprocessingdirective at the top, and no 
problem with charset.
Only with  the error handling page.



Original issue reported on code.google.com by jbc...@gmail.com on 24 Jul 2008 at 11:53

@GoogleCodeExporter
Copy link
Author

This must be a webserver configuration issue.  I cannot repro this on OpenBD.  
I see the correct output.  Based on the fact that no other user has reported 
this error, I am closing this issue.  If you experience this problem in the 
future, please include information about your OpenBD configuration and 
webserver setup. Also attach a simple set case that illustrates the problem.

Original comment by pe...@mach-ii.com on 29 Dec 2011 at 9:08

  • Changed state: Invalid
  • Added labels: Priority-Low
  • Removed labels: Priority-Medium

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant