Change proprietary headers format in the hint for Rule 183

[vadeg]

Proprietary headers in Rule 183 doesn't match Rule 132.

[tfrauenstein]

I think we should Rule 132 to the proprietary header section and include 'X-' prefixing -- Common / standard headers are anyway not in our naming responsibility. What additional concrete mismatches you see?

[vadeg]

Common / standard headers are anyway not in our naming responsibility

Then it could happen that we will see a lot of location instead of Location and accept-encoding instead of Accept-Encoding headers in APIs with arguments like "headers are case-insensitive anyways".

Should we mention in the Rule 133 than you should preserve naming convension for standard headers?

[tfrauenstein]

yes -- see my proposal #653

[tkrop]

Layout changes are transferred to #660.