Jonathan A. Sternberg 7a3bd19926 Properly use the 401 and 403 HTTP status codes ... According to the HTTP standard, a lack of authentication credentials or incorrect authentication credentials should send back a 401 (Unauthorized) with a `WWW-Authenticate` header with a challenge that can be used to authenticate. This is because a 401 status should be sent when an authentication attempt can be retried by the browser. The 403 (Forbidden) status code should be sent when authentication succeeded, but the user does not have the necessary authorization. Previously, the server would always send a 401 status code.		2016-07-07 20:30:04 -05:00
..
config.go	Properly use the 401 and 403 HTTP status codes	2016-07-07 20:30:04 -05:00
config_test.go	Update help and remove unused config options from the configuration file	2016-06-21 14:06:05 -05:00
handler.go	Properly use the 401 and 403 HTTP status codes	2016-07-07 20:30:04 -05:00
handler_test.go	Properly use the 401 and 403 HTTP status codes	2016-07-07 20:30:04 -05:00
listen.go	Teach the http service how to enforce connection limits	2016-05-12 16:25:16 -04:00
listen_test.go	Teach the http service how to enforce connection limits	2016-05-12 16:25:16 -04:00
response_logger.go	Removing dead code from every package except influxql	2016-06-20 22:41:07 -05:00
service.go	Refactoring the monitor service to avoid expvar	2016-07-07 11:13:58 -05:00