Robert says there is an X-Lazr-OopsID in failed api requests, so it is
already there in a reasonable form. At the moment I don't think
lazr.restful makes this available to the client and it probably
should, as should wrested.
This bug could be handled by clients looking for that header and
reporting it if it's present.
I still think it would be cleaner to not send html errors to api
clients. But obviously the clients do need to tolerate getting back
html that might come from an intermediate proxy or whatever.
Robert says there is an X-Lazr-OopsID in failed api requests, so it is
already there in a reasonable form. At the moment I don't think
lazr.restful makes this available to the client and it probably
should, as should wrested.
This bug could be handled by clients looking for that header and
reporting it if it's present.
I still think it would be cleaner to not send html errors to api
clients. But obviously the clients do need to tolerate getting back
html that might come from an intermediate proxy or whatever.