P
Peter Judge
Guest
Palinca is always welcome and appreciated 
As you know, different http headers can have different values. Some can be empty. Some must have a particular value. Some are integer values. Some have parameters. Content types must be something according to the rule Content-Type := type "/" subtype *[";" parameter] type := "application" / "audio" / "image" / "message" / "multipart" / "text" / "video" / x-token x-token := You cannot pass 'null' or an empty value etc, where the string 'null' may be valid for other headers. I am/was trying to come up with a solution that I could use for various headers, without having a type for each header (<-- this is also an option).
Continue reading...
As you know, different http headers can have different values. Some can be empty. Some must have a particular value. Some are integer values. Some have parameters. Content types must be something according to the rule Content-Type := type "/" subtype *[";" parameter] type := "application" / "audio" / "image" / "message" / "multipart" / "text" / "video" / x-token x-token := You cannot pass 'null' or an empty value etc, where the string 'null' may be valid for other headers. I am/was trying to come up with a solution that I could use for various headers, without having a type for each header (<-- this is also an option).Continue reading...