github-starred/yaak
2
0
Fork 0
mirror of https://github.com/mountain-loop/yaak.git synced 2026-05-06 07:52:20 -05:00
Code Issues 56 Packages Projects Releases 100 Wiki Activity

[PR #423] feat: Extract authentication when using the cURL importer #345

New Issue
Open
opened 2026-03-22 21:18:45 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-03-22 21:18:45 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/mountain-loop/yaak/pull/423
Author: @jeroenvandermerwe
Created: 3/11/2026
Status: 🔄 Open

Base: main ← Head: curl-authentication-header-extraction

📝 Commits (2)

  • 3c30f68 Implement authentication extraction from headers when using the cURL importer
  • fbc9630 Add tests for authorization header handling in cURL importer

📊 Changes

2 files changed (+222 additions, -6 deletions)

View changed files

📝 plugins/importer-curl/src/index.ts (+99 -6)
📝 plugins/importer-curl/tests/index.test.ts (+123 -0)

📄 Description

When importing a curl command, Authorization: Bearer <token> and Authorization: Basic <base64> headers are now extracted into the Authentication tab instead of being left in the Headers list.

  • Bearer tokens → Bearer authentication type (RFC 6750)
  • Basic auth → Basic authentication type with decoded username/password (RFC 7617)
  • Header-based authentication takes precedence over -u/--user flags
  • Non-standard schemes remain in Headers as before

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/mountain-loop/yaak/pull/423 **Author:** [@jeroenvandermerwe](https://github.com/jeroenvandermerwe) **Created:** 3/11/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `curl-authentication-header-extraction` --- ### 📝 Commits (2) - [`3c30f68`](https://github.com/mountain-loop/yaak/commit/3c30f68c5505d074692dafc955deceedd5249af4) Implement authentication extraction from headers when using the cURL importer - [`fbc9630`](https://github.com/mountain-loop/yaak/commit/fbc9630f067a11ccec923da9c3757e2b5559ba37) Add tests for authorization header handling in cURL importer ### 📊 Changes **2 files changed** (+222 additions, -6 deletions) <details> <summary>View changed files</summary> 📝 `plugins/importer-curl/src/index.ts` (+99 -6) 📝 `plugins/importer-curl/tests/index.test.ts` (+123 -0) </details> ### 📄 Description When importing a curl command, `Authorization: Bearer <token>` and `Authorization: Basic <base64>` headers are now extracted into the Authentication tab instead of being left in the Headers list. - Bearer tokens → Bearer authentication type (RFC 6750) - Basic auth → Basic authentication type with decoded username/password (RFC 7617) - Header-based authentication takes precedence over `-u/--user` flags - Non-standard schemes remain in Headers as before --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-03-22 21:18:45 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
pull-request
Mirrored from GitHub Pull Request
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/yaak#345
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?