Changes between Version 20 and Version 21 of S3XRC/ResourceReport


Ignore:
Timestamp:
08/28/10 19:49:25 (14 years ago)
Author:
Dominic König
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • S3XRC/ResourceReport

    v20 v21  
    103103}}}
    104104
    105 It is important to raise a HTTP error in case of an unsupported format rather than providing a nicely formatted error message to the user: while an interactive user who just clicks on links and buttons would rarely request something else than HTML - it would rather be a non-interactive client which requests other formats, and that would hardly understand a nicely formatted error message but expects a proper HTTP status in the response header.
     105It is important to raise a HTTP error in case of an unsupported format rather than providing a nicely formatted error message to the user: while an interactive user who just clicks on links and buttons would rarely request something else than the interactive formats we expose to him - it would rather be a non-interactive client which requests other formats, and that would hardly understand a nicely formatted error message but expect a proper HTTP status in the response header.
    106106==== Get at the data ====
    107107