mirror of
				https://github.com/ossrs/srs.git
				synced 2025-03-09 15:49:59 +00:00 
			
		
		
		
	Word the comments about the order of HTTP header
This commit is contained in:
		
							parent
							
								
									0886acbdb7
								
							
						
					
					
						commit
						547cd4f518
					
				
					 1 changed files with 5 additions and 0 deletions
				
			
		| 
						 | 
				
			
			@ -108,6 +108,11 @@ enum SrsHttpParseState {
 | 
			
		|||
class SrsHttpHeader
 | 
			
		||||
{
 | 
			
		||||
private:
 | 
			
		||||
    // The order in which header fields with differing field names are
 | 
			
		||||
    // received is not significant. However, it is "good practice" to send
 | 
			
		||||
    // general-header fields first, followed by request-header or response-
 | 
			
		||||
    // header fields, and ending with the entity-header fields.
 | 
			
		||||
    // @doc https://tools.ietf.org/html/rfc2616#section-4.2
 | 
			
		||||
    std::map<std::string, std::string> headers;
 | 
			
		||||
public:
 | 
			
		||||
    SrsHttpHeader();
 | 
			
		||||
| 
						 | 
				
			
			
 | 
			
		|||
		Loading…
	
	Add table
		Add a link
		
	
		Reference in a new issue