Skip to main content
added 11 characters in body
Source Link
Philipp
  • 23.4k
  • 6
  • 64
  • 68

When the information is important, you should put it into the body.

Why?

  1. proxy servers are allowed to modify headers. Many are configured to strip any headers they don't know. This, however, only applies when you use unencrypted HTTP. When you use HTTPS, the proxy can't change the headers because they are encrypted.
  2. When you use a webservice, you usually do so for interoperability with other devices, services and tools. Most APIs and tools which work with webservices can easily change requests, but many make it difficult or even impossible to add custom headers. This, of course, only applies when interoperability is a concern. But when you don't care, you might want to ask yourself why you are using webservices in the first place instead of just building your own protocol on raw TCP.

When the information is important, you should put it into the body.

Why?

  1. proxy servers are allowed to modify headers. Many are configured to strip any headers they don't know. This, however, only applies when you use unencrypted HTTP. When you use HTTPS, the proxy can't change the headers because they are encrypted.
  2. When you use a webservice, you usually do so for interoperability with other devices, services and tools. Most APIs and tools which work with webservices can easily change requests, but many make it difficult or even impossible to add custom headers. This, of course, only applies when interoperability is a concern. But when you don't care, you might want to ask yourself why you are using webservices in the first place instead of just building your own protocol.

When the information is important, you should put it into the body.

Why?

  1. proxy servers are allowed to modify headers. Many are configured to strip any headers they don't know. This, however, only applies when you use unencrypted HTTP. When you use HTTPS, the proxy can't change the headers because they are encrypted.
  2. When you use a webservice, you usually do so for interoperability with other devices, services and tools. Most APIs and tools which work with webservices can easily change requests, but many make it difficult or even impossible to add custom headers. This, of course, only applies when interoperability is a concern. But when you don't care, you might want to ask yourself why you are using webservices in the first place instead of just building your own protocol on raw TCP.
Post Undeleted by Philipp
added 427 characters in body
Source Link
Philipp
  • 23.4k
  • 6
  • 64
  • 68

When the information is important, you should put it into the body.

Why?

  1. proxy servers are allowed to modify headers. Many are configured to strip any headers they don't know. This, however, only applies when you use unencrypted HTTP. When you use HTTPS, the proxy can't change the headers because they are encrypted.
  2. When you use a webservice, you usually do so for interoperability with other devices, services and tools. Most APIs and tools which work with webservices can easily change requests, but many make it difficult or even impossible to add custom headers. This, of course, only applies when interoperability is a concern. But when you don't care, you might want to ask yourself why you are using webservices in the first place instead of just building your own protocol.

This, however, only applies when you use unencrypted HTTP. When you use HTTPS, the

When the information is important, you should put it into the body.

Why?

  1. proxy servers are allowed to modify headers. Many are configured to strip any headers they don't know.

This, however, only applies when you use unencrypted HTTP. When you use HTTPS, the

When the information is important, you should put it into the body.

Why?

  1. proxy servers are allowed to modify headers. Many are configured to strip any headers they don't know. This, however, only applies when you use unencrypted HTTP. When you use HTTPS, the proxy can't change the headers because they are encrypted.
  2. When you use a webservice, you usually do so for interoperability with other devices, services and tools. Most APIs and tools which work with webservices can easily change requests, but many make it difficult or even impossible to add custom headers. This, of course, only applies when interoperability is a concern. But when you don't care, you might want to ask yourself why you are using webservices in the first place instead of just building your own protocol.
Post Deleted by Philipp
Source Link
Philipp
  • 23.4k
  • 6
  • 64
  • 68

When the information is important, you should put it into the body.

Why?

  1. proxy servers are allowed to modify headers. Many are configured to strip any headers they don't know.

This, however, only applies when you use unencrypted HTTP. When you use HTTPS, the