Context Navigation

Changes between Version 21 and Version 22 of S3XRC/ResourceReport

v21	v22
103	103	}}}
104	104
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 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.
	105	''It is important to raise a HTTP error in case of an unsupported format rather than providing a nicely formatted error message in response: 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.''
106	106	==== Get at the data ====
107	107