All geek questions in one place

Why does x-www-form-urlencoded begin with x-www when there are no other types of standard content?

I understand that in the past it was standard for user header names to use the prefix "X-" (I know that it is no longer considered standard for this), but I could not find if there is any relationship between this naming convention and value ("application / x-www-form-urlencoded"). Did it start as a custom value for a content type that was later adopted, or something else?

I found this link here, which, of course, was interesting, but could not find the answer to my question.

Does anyone know the reason this prefix was chosen, and what does it mean?

+4
source share
2 answers

it was standard for custom header names to use the prefix "X -"

Actually ... no, not at all. To be precise: it was never the standard, but only the best practice. This allowed developers to introduce new types of content and encodings without having to write the entire RFC for it. Currently, the IANA Media Type Registry is suitable for this . RFC 6648 put an end to this practice.

application/x-www-form-urlencoded ( MIME , btw)) , "" URL-. . , HTML, , .

+3

, , x-, Mosaic - , x- . , , , .

1993 www-talk " " -1993 :

, Mosaic 2.0... .

http://www.ncsa.uiuc.edu/SDG/Software/Mosaic/Docs/fill-out-forms/overview.html

... ,

, " 2.0 X 2.0" archive.org. :

ENCTYPE . , METHOD POST - ( , application/x-www-form-urlencoded).

application/x-www-form-urlencoded URL, - :

application/x-www-form-urlencoded , , , , . , , ( ) . , - HTML-.

+2

Source: https://habr.com/ru/post/1669937/

More articles:


All Articles