server icon indicating copy to clipboard operation
server copied to clipboard

add the -L parameter to fix #5934

Open is opened this issue 1 year ago • 9 comments

as title.

is avatar Jun 12 '23 16:06 is

Should the target branch be main instead of r23.05?

GuanLuo avatar Jun 14 '23 21:06 GuanLuo

Should the target branch be main instead of r23.05?

Shall I switch the target branch to main now?

is avatar Jun 15 '23 01:06 is

Honestly I don't see a reason why we need to change the instructions by adding -L/--location key.

-L/--location (HTTP/HTTPS) If the server reports that the requested page has moved to a different location (indicated with a Location: header and a 3XX response code), this option will make curl redo the request on the new place. If used together with -i/--include or -I/--head, headers from all requested pages will be shown. When authentication is used, curl only sends its credentials to the initial host. If a redirect takes curl to a different host, it won't be able to intercept the user+password. See also --location-trusted on how to change this. You can limit the amount of redirects to follow by using the --max-redirs option. When curl follows a redirect and the request is not a plain GET (for example POST or PUT), it will do the following request with a GET if the HTTP response was 301, 302, or 303. If the response code was any other 3xx code, curl will re-send the following request using the same unmodified method.

We had never observed redirection request on this instruction.

@is are you faced any issues on this request/instruction layer?

cc: @GuanLuo

mc-nv avatar Jul 21 '23 22:07 mc-nv

Hi @mc-nv In china, all download request to https://developer.download.nvidia.com/ will be redirect to https://developer.download.nvidia.cn/, so need the -L option to follow the redirection.

is avatar Jul 22 '23 03:07 is

@is Sorry for the late response, yes, please switch the target branch to main. You may need to rebase / resolve merge conflicts if GitHub reports any.

GuanLuo avatar Aug 08 '23 23:08 GuanLuo

@is Sorry for the late response, yes, please switch the target branch to main. You may need to rebase / resolve merge conflicts if GitHub reports any.

I rebase the PR onto last main branch.

is avatar Aug 11 '23 00:08 is

Looks like this is also a duplicate of https://github.com/triton-inference-server/server/pull/6099

rmccorm4 avatar Feb 09 '24 20:02 rmccorm4

@is did you fill out a CLA as described here: https://github.com/triton-inference-server/server/blob/main/CONTRIBUTING.md#contributor-license-agreement-cla?

rmccorm4 avatar Feb 09 '24 20:02 rmccorm4

Hi @rmccorm4, From the relevant discussions I've seen, it seems you want to address the issue at a more fundamental level. Does this mean there's no urgency to sign the protocol for now?

is avatar Feb 19 '24 12:02 is