8000 Feature Request: Specify if a workflow should use proxy or not · Issue #10298 · MISP/MISP · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Feature Request: Specify if a workflow should use proxy or not #10298

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.

Sign up for GitHub

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

Jump to bottom
Open
9C94 1 task done
SanjyASZ opened this issue Apr 7, 2025 · 0 comments
Open
1 task done

Feature Request: Specify if a workflow should use proxy or not #10298

SanjyASZ opened this issue Apr 7, 2025 · 0 comments
Labels
needs triage This issue has been automatically labelled and needs further triage T: feature request Type: feature request. This issue is requesting a new feature

Comments

@SanjyASZ
Copy link
SanjyASZ commented Apr 7, 2025 •
edited
Loading

Hi,

Right now there is no way for a misp workflow to specify to use the proxy (global settings) or not.

Kinda similar to this issue but with workflow
#5186

Describe the solution you'd like

Use a "skip proxy" checkbox in the workflow settings or in node of the workflow.

Describe alternatives you've considered

No response

Additional context

WORKFLOW, PROXY, URL

Code of Conduct

  • I agree to follow this project's Code of Conduct
@SanjyASZ SanjyASZ added needs triage This issue has been automatically labelled and needs further triage T: feature request Type: feature request. This issue is requesting a new feature labels Apr 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
needs triage This issue has been automatically labelled and needs further triage T: feature request Type: feature request. This issue is requesting a new feature
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@SanjyASZ
0