REST APIs: custom HTTP headers vs URL parameters

问题:

When do you use custom HTTP headers in the request part of a REST API ?

Example:

Would you ever use

GET /orders/view 
(custom HTTP header) CLIENT_ID: 23

instead of

GET /orders/view/client_id/23 or 
GET /orders/view/?client_id=23

回答1:

The URL indicates the resource itself. A "client" is a resource that can be acted upon, so should be part of the base url: /orders/view/client/23.

Parameters are just that, to parameterize access to the resource. This especially comes into play with posts and searches: /orders/find?q=blahblah&sort=foo. There's a fine line between parameters and sub-resources: /orders/view/client/23/active versus /orders/view/client/23?show=active. I recommend the sub-resource style and reserve parameters for searches.

Since each endpoint REpresents a State Transfer (to mangle the mnemonic), custom headers should only be used for things that don't involve the name of the resource (the url), the state of the resource (the body), or parameters directly affecting the resource (parameters). That leaves true metadata about the request for custom headers.

HTTP has a very wide selection of headers that cover most everything you'll need. Where I've seen custom headers come up is in a system to system request operating on behalf of a user. The proxy system will validate the user and add "X-User: userid" to the headers and use the system credentials to hit the endpoint. The receiving system validates that the system credentials are authorized to act on behalf of the user, then validate that the user is authorized to perform the action.

回答2:

I would only use a custom header when there is no other way to pass information by standard or convention. Darren102 is explaining the typical way to pass that value. Your Api will be much more friendly by using typical patterns verse using custom headers.That's not to say you won't have a case to use them, just that they should be the last resort and something not already handled by the HTTP spec.

回答3:

Custom headers have the following advantages:

• Can be read easily by network tools/scripts (authentication, meta info, ...)
• Keeps urls free from security stuff (safer, not in browser/proxy caches)
• Keeps urls cleaner: allows for better caching of resources

回答4:

When do you use...HTTP headers in the request part of a REST API?

Authentication: GUIDs, basic authentication, custom tokens, etc. e.g., Basic Authentication with a Guid token for REST api instead of username/password

If you get involved in passing tokens or other authentication-like information between domains covered by PCI-DSS or other security rules you may also have to bury parameters because some regulations explicitly require authentication elements to stay out of URLs that could be trivially replayed (from browser histories, proxy logs, etc.).

回答5:

I wouldn't use custom headers as you don't know if any proxies will pass those on. URL based is the way to go.

GET /orders/view/client/23

回答6:

There is no standard for REST however the accepted way would be

GET /orders/view/23

Not using the custom headers and hence the 23 after view assumes to be the id hence you would have a function that takes in the id and hence produces just that information.

回答7:

Definitely OK:

GET /orders/view/client_id/23 or 
GET /orders/view/?client_id=23

Also OK:

GET /orders/view/23 or 

I would think this would be OK, too:

POST /orders/view 
(custom HTTP header) CLIENT_ID: 23

回答8:

You can use custom headers to include more information about a partially processed request considering that Enveloping is not a good practice. The headers are secure.