Added: 1 year ago
From: thehegarty87
Views: 578
Sort by time | Sort by thread (beta)

Link to this comment:

Share to:

All Comments (29)

Sign In or Sign Up now to post a comment!
  • If the message is received with a transfer-encoding, that encoding MUST be removed prior to checking the Content-MD5 value against the received entity.

  • The MD5 digest is computed based on the content of the entity-body,

     including any content-coding that has been applied, but not including any transfer-encoding applied to the message-body.

  • Only origin servers or clients MAY generate the Content-MD5 header field; proxies and gateways MUST NOT generate it, as this would defeat its value as an end-to-end integrity check. Any recipient of the entity- body, including gateways and proxies, MAY check that the digest value in this header field matches that of the entity-body as received.

  • The Content-MD5 header field MAY be generated by an origin server or client to function as an integrity check of the entity-body.

  • (Note: a MIC is good for detecting accidental modification of the entity-body in transit, but is not proof against malicious attacks.)

  • 14.15 Content-MD5 The Content-MD5 entity-header field, as defined in RFC 1864 [23], is an MD5 digest of the entity-body for the purpose of providing an  end-to-end message integrity check (MIC) of the entity-body.

  • The meaning of the Content-Location header in PUT or POST requests is undefined; servers are free to ignore it in those cases.

  • If the Content-Location is a relative URI, the relative URI is interpreted relative to the Request-URI.

  • However, the Content- Location can be used to differentiate between multiple entities

     retrieved from a single requested resource, as described in section 13.6.

  • A cache cannot assume that an entity with a Content-Location different from the URI used to retrieve it can be used to respond to later requests on that Content-Location URI.

  • Future requests MAY specify the Content-Location URI as the request- URI if the desire is to identify the source of that particular entity.

  • The Content-Location value is not a replacement for the original requested URI; it is only a statement of the location of the resource corresponding to this particular entity at the time of the request.

  • The value of Content-Location also defines the base URI for the  entity.

  • A server SHOULD provide a Content-Location for the variant corresponding to the response entity; especially in the case where a resource has multiple entities associated with it, and those entities actually have separate locations by which they might be individually accessed, the server SHOULD provide a Content-Location for the particular variant which is returned.

  • ill pop a glock in your mouth a make a brain slushie

  • Haha xD nice and simple!!

    I did a rant on this chick recently and then a few days later I found out she's at it again on tinychat, some people never learn haha.

  • jenni slaugter is a only tiny and stupid girl, like the many others. she doesnt know what she say, please, how much old are you. think about it.

  • ur late.

  • Thnx 4 the comment & thnx 4 the lmfao..lol..Rockin Robin Rox supports back!

  • To Funny I like the effects !! Thumbs up !!

  • I think:

    She is probably regretting what she did right now, albeit an annoying 11 year old girl.

  • nice effect

  • I don't know who is Jessi Slaughter ;p

  • You dun goof'd

  • Lmfao XD

  • funny! lol i also liked the effects and "thumbed-up" it :D

  • i like the effects of this new video.

Loading...
Alert icon
0 / 00Unsaved Playlist Return to active list
    1. Your queue is empty. Add videos to your queue using this button:
      or sign in to load a different list.
    Loading...Loading...Saving...
    • Clear all videos from this list
    • Learn more