-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
'actions/checkout@v4' with LFS fails because of double auth header #1830
Comments
For anyone interested here's a workaround to get this to work: - uses: actions/checkout@v4
with:
persist-credentials: 'true' # Optional; should be the default
- name: Checkout lfs
run: |
git lfs install --local
AUTH=$(git config --local http.${{ github.server_url }}/.extraheader)
git config --local --unset http.${{ github.server_url }}/.extraheader
git config --local http.${{ github.server_url }}/${{ github.repository }}.git/info/lfs/objects/batch.extraheader "$AUTH"
git lfs pull |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am encountering an issue with the Git LFS integration in my Workflow. The problem involves the sending of double Authorization headers in HTTP requests, which results in a 400 Bad Request error. This issue is preventing successful data transfers and impacting the workflow execution. The problem mainly occurs in my submodules, since these require Git LFS.
The first LFS batch request works without problem and I see only one basic authorization.
Error Log
Here is a snippet from the workflow logs that illustrates the issue:
Steps to Reproduce
Expected Behavior
The HTTP requests made by Git LFS should include only a single Authorization header.
Actual Behavior
The HTTP requests include two Authorization headers, leading to a 400 Bad Request error.
More information about this issue:
https://gitea.com/gitea/act_runner/issues/164#issue-194072
https://gitea.com/gitea/act_runner/issues/164#issuecomment-739866
https://gitea.com/gitea/act_runner/issues/164#issuecomment-836693
The text was updated successfully, but these errors were encountered: