Stack Overflow
Stack Overflow

Questions tagged [rfc2616]

An RFC entitled "Hypertext Transfer Protocol -- HTTP/1.1"

See for more details on RFC

RFC 2616 was released in june 1999 and supersedes RFC 2068.

Resources:

71 questions
2
votes
2 answers

Is it possible to suggest an update to RFC?

Section 4, page 34: If the message uses the media type "multipart/byteranges", and the ransfer-length is not otherwise specified, then this self- ^ should be transfer instead? elimiting media type defines the transfer-length.…
Tarasovych
  • 2,228
  • 3
  • 19
  • 51
2
votes
1 answer

RFCs for implementing HTTP server

I'm thinking to start a side project to learn how HTTP servers are built. I started searching for it and came to know that the specifications are mentioned in RFC documents. But there are over 8200 RFCs as of August 2017. Further searching about it…
SkrewEverything
  • 2,393
  • 1
  • 19
  • 50
2
votes
0 answers

Trusting content type from a client

I have seen the answers on this SO question: Trusting "Content-Type" on File Uploads And they make sense intuitively. However, according to RFC 2616 Sec 7.2.1, "If and only if the media type is not given by a Content-Type field, the recipient…
Vasan
  • 4,810
  • 4
  • 20
  • 39
2
votes
2 answers

Is there ever any reason to respond with "Vary: *" and "Vary: Foo" for the same resource?

Is there any reason for a HTTP server to sometimes respond with Vary: *, and sometimes with Vary: Foo, to requests for the same resource? What should a cache do, if after receiving (and caching) both responses, it then receives a request with a…
mjs
  • 63,493
  • 27
  • 91
  • 122
2
votes
0 answers

Would it be a good idea to return the Allow HTTP Header in response to a GET/PUT/POST/PATCH/HEAD methods as well

Per RFC2616 The Allow entity-header field lists the set of methods supported by the resource identified by the Request-URI. The purpose of this field is strictly to inform the recipient of valid methods associated with the resource. It mandates…
g7p
  • 116
  • 5
2
votes
1 answer

Is there a way to disable byte-range requests on the client side?

I understand that one can set Accept-Ranges: none on the server to advise the client not to attempt a range request. I am wondering if there is a way to tell a browser not to attempt a range request without having to make any changes on the…
Olaide Oyekoya
  • 83
  • 7
2
votes
1 answer

How is determining body length by closing connection reliable (RFC 2616 4.4.5)

I can't get one thing straight. The RFC 2616 in 4.4.5 states that Message Length can be determined "By the server closing the connection.". This implies, that it is valid for a server to respond (e.g. returning a large image) with a response, that…
Bartek Chlebek
  • 1,665
  • 1
  • 16
  • 23
2
votes
1 answer

Win32: What is the status of chunked encoding support in WinHttpReadData?

The documentation for WinHttpReadData says, regarding HTTP's chunked transfer coding: Starting in Windows Vista and Windows Server 2008, WinHttp enables applications to perform chunked transfer encoding on data sent to the server. When the…
Cheeso
  • 189,189
  • 101
  • 473
  • 713
2
votes
1 answer

HTTP 1.1 TE header

While reading RFC2616, I came across TE and Transfer Encoding headers for chunked encoding. I have following question on these: If a HTTP Server rejects a request because of presence of TE header, is it RFC compliant? If a HTTP Client sends a…
Vamsi Mohan
  • 307
  • 1
  • 5
  • 13
2
votes
1 answer

Flask: Implementing a HTTP GET with an array parameter

I am implementing an HTTP REST API which contains a /feed request. The request returns a user's news feed. The request comes with a few parameters, including the userId, a list of followers, startTime and maxItems. The easiest way to implement it…
Adam Matan
  • 128,757
  • 147
  • 397
  • 562
2
votes
1 answer

How should an HTTP server handle If-Unmodified-Since with multiple changes within one second?

The HTTP Spec (RFC-2616) states in section 14.28 that the If-Unmodified-Since header MUST be recognized by an HTTP server and that it has only a precision of one second. How should a server handle this header, if the resource changes more often than…
h2stein
  • 546
  • 3
  • 13
2
votes
1 answer

Hyperlinks in the body of a 303 response

When doing 303 redirects after a POST, RFC 2616 mentions adding a hyperlink in the body of the response (i.e. the POST's 303 response body, not the response of the subsequent GET on newly created resource). 10.3.4 303 See Other The response to the…
deontologician
  • 2,764
  • 1
  • 21
  • 33
2
votes
1 answer

Embedded HTTPS server. How should redirection be handled, and should I offer HTTP?

Background I have implemented a HTTPS server which sits inside a piece of hardware for the purpose of secure remote configuration of the device. To achieve this, I have used an existing lightweight embedded TCP/IP stack together with an open source…
Trevor
  • 10,903
  • 5
  • 61
  • 84
1
vote
1 answer

RFC2616 13.3, Browser History and Caching

I've been trying to get my head around the whole issue of browser history Vs caching and RFC2616 13.13 Does this section of the RFC mean that if a user goes "Back" in the browser, for example, it should always display the page from it's local…
Andy Birchall
  • 311
  • 1
  • 3
  • 12
1
vote
1 answer

Can I separate ALL HTTP headers with a comma? Even Authorization?

I am reading through the HTTP 1.1 RFCs and I am not able to answer the following question. We have this header: Authorization: Basic Qmxvb21iZXJnOnRjbG1lU1JT, Basic which is causing troubles because Rails 3 authorization parser incorrectly decodes…
lzap
  • 16,417
  • 12
  • 71
  • 108
1 2
3
4 5