Reed Allman 97194b3d8b return bad function http resp error (#728) ...

* return bad function http resp error

this was being thrown into the fn server logs but it's relatively easy to get
this to crop up if a function user forgets that they left a `println` laying
around that gets written to stdout, it garbles the http (or json, in its case)
output and they just see 'internal server error'. for certain clients i could
see that we really do want to keep this as 'internal server error' but for
things like e.g. docker image not authorized we're showing that in the
response, so this seems apt.

json likely needs the same treatment, will file a bug.

as always, my error messages are rarely helpful enough, help me please :)

closes #355

* add formatting directive

* fix up http error

* output bad jasons to user

closes #729

woo

2018-02-12 17:51:45 -08:00

..

default.go

Update json (#463)

2017-11-16 09:59:13 -08:00

factory.go

Hot protocols improvements (for 662) (#724)

2018-01-31 12:26:43 +00:00

http.go

return bad function http resp error (#728)

2018-02-12 17:51:45 -08:00

json_test.go

Hot protocols improvements (for 662) (#724)

2018-01-31 12:26:43 +00:00

json.go

return bad function http resp error (#728)

2018-02-12 17:51:45 -08:00