this post was submitted on 21 Jul 2024
19 points (100.0% liked)
Learn Programming
1625 readers
1 users here now
Posting Etiquette
-
Ask the main part of your question in the title. This should be concise but informative.
-
Provide everything up front. Don't make people fish for more details in the comments. Provide background information and examples.
-
Be present for follow up questions. Don't ask for help and run away. Stick around to answer questions and provide more details.
-
Ask about the problem you're trying to solve. Don't focus too much on debugging your exact solution, as you may be going down the wrong path. Include as much information as you can about what you ultimately are trying to achieve. See more on this here: https://xyproblem.info/
Icon base by Delapouite under CC BY 3.0 with modifications to add a gradient
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
The majority of HTTP frameworks I’ve used store headers in a dictionary, because the common denominator between all headers is that they are string keys and string values.
To clarify: you might think that some headers are lists of strings, but that’s not actually true - the user can send any string to you. You really open yourself up to parsing problems if somebody transmits a header in a format that cannot be represented by your data structure.
Oftentimes what a framework will do is store the headers in the dictionary, and then provide getters and setters to access “friendly” parsed versions of commonly used data (but only if it parses correctly).
What do you mean by this? And where is the header processing done? And btw thanks for your answer, I knew I was doing something wrong.
Edit: Are the possible options for headers stored in for example a header class, or are they just checked when clients are processed?
So for example in “requests”, a popular http framework in Python, there’s a class for the Response object. On that object you can access the special header dictionary at
response.headers
. Check the docs here under the section Response HeadersBasically they make a special dictionary that allows headers to be case-insensitive, and combining headers that are provided twice.
But they also provide a special property
response.encoding
which derives from the Content-Type header, just for convenience.Hopefully that all makes sense.