0 user Sign-in to change your status

Renders exceptions as the appropriate content type. WebServices

• Repository
• Download package
• Browse source

Renders exceptions in the request format.

Developers

Name	Status	Email
Kris Wallsmith	lead	moc.tcejorp-ynofmys <<ta>> htimsllaw.sirk

License

Copyright (c) 2008 Kris Wallsmith

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Releases for sf 1.1

Join this plugin team

Other releases

Release 1.0.0 - 09/09/2008

The sfExceptionFormatsPlugin extends symfony 1.1's integration of multiple request formats to include exception and error 500 pages.

For example, if a request that includes a sf_method parameter with the value of xml throws an exception, the plugin will output the following response:

<?xml version="1.0" encoding="UTF-8"?>
<error code="500" message="Internal Server Error"/>

Very little information is betrayed here. If you request the same URL using a debug controller, you will see a bit more:

<?xml version="1.0" encoding="UTF-8"?>
<error code="500" message="Internal Server Error">
  <debug exception="sfException" message="Something unexpected happened" />
</error>

Customizing the error responses

You can easily customize how exceptions for each format are rendered by adding a template file to your project or application's config directory. For example, placing a exception.json.php file in /config will customize how JSON exceptions are rendered when debug mode is on. An error_500.json.php file in the same directory would render when debug mode is off.

The offending exception object is available in all custom templates as $exception.