Instruct to set NO_PROXY to avoid LAPI errors#775
Merged
LaurenceJJones merged 1 commit intocrowdsecurity:mainfrom May 2, 2025
Merged
Instruct to set NO_PROXY to avoid LAPI errors#775LaurenceJJones merged 1 commit intocrowdsecurity:mainfrom
LaurenceJJones merged 1 commit intocrowdsecurity:mainfrom
Conversation
|
This pull request is automatically being deployed by Amplify Hosting (learn more). |
LaurenceJJones
approved these changes
May 2, 2025
Contributor
|
Hey 👋🏻 Thank you for opening a pull request! Merged as it quite useful as when we tested it, I believe the go package by default ignores loopback requests but 🤷🏻 we should explicitly ignore them via configuration. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Without explicitly setting
NO_PROXY=127.0.0.1,localhost,0.0.0.0, LAPI will throw an error: