Robert Estelle 6ff0868457 http: Response refers to requested ETag on 304, not 200 ...

Otherwise a 200 response without an ETag could be incorrectly associated
to previous content in the following scenario:

* The remote server had in the past responded with an ETag for this
  resource, which was cached.
  - (Otherwise, onlyETag would be empty)
* That was the only ETag cached for this resource.
  - (Otherwise, onlyETag would be empty)
* The remote server then stopped supporting ETag/If-None-Match for this
  resource at all.
  - (Otherwise, it would respond with a 304 or a 200+ETag)

Signed-off-by: Robert Estelle <robertestelle@gmail.com>

2019-09-04 20:25:53 -04:00

..

containerimage

Merge pull request #1024 from tonistiigi/gcr-workaround

2019-06-17 10:36:49 -07:00

git

git: updates for keep git dir

2019-08-14 13:28:42 -07:00

http

http: Response refers to requested ETag on 304, not 200

2019-09-04 20:25:53 -04:00

local

local: handle canceled uploads

2019-05-28 14:06:17 -07:00

gitidentifier.go

Clean some small dependencies on docker/docker package

2018-02-01 16:05:24 -08:00

identifier.go

source: Have ResolveMode implement fmt.Stringer interface

2018-08-17 14:33:34 +00:00

manager.go

decouple SessionManager from Worker

2019-02-23 22:55:17 +09:00