What steps will reproduce the problem?
1. run prosody with http module
2. curl -I 127.0.0.1:5280/foobar
What is the expected output?
HTTP/1.1 404 Not Found
Connection: Keep-Alive
Content-Length: 398
Content-Type: text/html; charset=utf-8
Date: Thu, 26 Oct 2017 10:28:45 GMT
What do you see instead?
HTTP/1.1 404 Not Found
Connection: Keep-Alive
Content-Length: 398
Date: Thu, 26 Oct 2017 10:28:45 GMT
What version of the product are you using? On what operating system?
0.10 @ Debian 8
Please provide any additional information below.
-
Zash
on
Thanks for the report. Fixed in https://hg.prosody.im/0.10/rev/e2460edc2a2f
However due to how error handling works, uncaught exceptions will still produce a '500 Internal Server Error' page without a content type.
What steps will reproduce the problem? 1. run prosody with http module 2. curl -I 127.0.0.1:5280/foobar What is the expected output? HTTP/1.1 404 Not Found Connection: Keep-Alive Content-Length: 398 Content-Type: text/html; charset=utf-8 Date: Thu, 26 Oct 2017 10:28:45 GMT What do you see instead? HTTP/1.1 404 Not Found Connection: Keep-Alive Content-Length: 398 Date: Thu, 26 Oct 2017 10:28:45 GMT What version of the product are you using? On what operating system? 0.10 @ Debian 8 Please provide any additional information below. -
Thanks for the report. Fixed in https://hg.prosody.im/0.10/rev/e2460edc2a2f However due to how error handling works, uncaught exceptions will still produce a '500 Internal Server Error' page without a content type.
Changes