You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Packfile URIs require a scheme and authority even when the pack and the
repository are served by the same HTTP(S) server.
Allow the server to advertise an absolute-path reference, as defined by
RFC 3986, section 4.2 [1]. Resolve it using the remote's scheme and
authority, following section 5.2.2 [2]. For example, /foo.pack from
https://example.com/repo.git resolves to https://example.com/foo.pack.
Packfile URIs do not support local paths, so there is no ambiguity with
a local file named /foo.pack.
Add a separate packfile-uris-absolute-path fetch capability. The client
declares support only for HTTP(S) remotes whose scheme is allowed by
fetch.uriprotocols. This flag does not change the server's URI selection.
When uploadpack.blobPackfileUri contains an absolute-path reference,
reject packfile-URI requests without the flag before starting
pack-objects. Leave fetches that do not request packfile URIs unchanged.
Handle only references beginning with a single slash. Redact their paths
in packet traces, as we do for absolute URIs.
[1] https://www.rfc-editor.org/rfc/rfc3986.html#section-4.2
[2] https://www.rfc-editor.org/rfc/rfc3986.html#section-5.2.2
Signed-off-by: Friel <friel@openai.com>
0 commit comments