Derek McGowan

@JaviSabalete thanks for report and testing the release candidate. While I look into this do you mind putting the registry in debug mode and including the debug logs.

@JaviSabalete unable to reproduce. Please add `-e REGISTRY_LOGLEVEL=debug` to the command and send the result. The trace should have more information as to where the invalid path error occurred.

@JaviSabalete thanks! It is this call to `Stat` which is erroring out ``` time="2017-01-05T11:55:24Z" level=debug msg="s3aws.Stat(\"/docker/registry/v2/repositories/\")" go.version=go1.7.3 http.request.host="MYREGISTRYURL:5000" http.request.id=229b2b83-64eb-4155-83be-334a8a2ff8b1 http.request.method=GET http.request.remoteaddr="MYIP:38167" http.request.uri="/v2/_catalog" http.request.useragent="Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko)...

Ok, I was able to reproduce this issue by doing ``` $ aws s3 cp somefile "s3://mybucket/docker/registry/v2/repositories//" ``` This "empty" directory name causes results to be returned from `List` which...

> No empty directory on this folder Did you see anything under the directory that wasn't part of a repository name or wouldn't match the regexp I sent? > Probably...

> I discovered that a pem-formatted rootcertbundle is required to start the registry with token authentication (I didn't see the PEM format requirement of this file documented anywhere) We should...

@marcellodesales the difficult part is going to be getting web login support within the docker client. I have everything else prototyped and working based on this specification. This specification will...

This is not included in 1.13 (registry 2.6), let me tentatively add it to the 2.7 milestone

@TheJayMann the original proposal is kind of old. The part that was ended to be solved by the `HEAD` is the zero-knowledge problem we have from Docker clients today. There...

Updated, also renamed "nameComponentRegexp" to "pathComponentRegexp" to match the grammar