Project

General

Profile

Actions
Copy link

Bug #3863

closed

nfd-status-http-server: HTTP status 200 when NFD is not running

Added by Junxiao Shi about 8 years ago. Updated about 8 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Junxiao Shi
Category:
Tools
Target version:
v0.6
Start date:
11/23/2016
Due date:
% Done:

100%

Estimated time:
0.50 h

Description

Steps to reproduce:

  1. nfd-stop
  2. nfd-status-http-server
  3. curl -v http://localhost:8080/

Actual: HTTP response status is 200
Expected: HTTP response status is in 5xx range

RFC2616 defines "200 OK" to mean "the request has succeeded", but this is not the case when NFD status isn't retrieved.

Actions
Copy link
 #1

Updated by Junxiao Shi about 8 years ago

I think 504 Gateway Timeout is the most suitable code, in the sense that nfd-status-http-server acts as a proxy between NFD-Management and HTTP server.

Actions
Copy link
 #2

Updated by Junxiao Shi about 8 years ago

  • Status changed from New to In Progress
  • Assignee set to Junxiao Shi
Actions
Copy link
 #3

Updated by Junxiao Shi about 8 years ago

  • Status changed from In Progress to Code review
  • % Done changed from 0 to 100
Actions
Copy link
 #4

Updated by Junxiao Shi about 8 years ago

  • Status changed from Code review to Closed
Actions
Copy link

Also available in: Atom PDF