Making app CNAME optional #155
Merged
Conversation
This file contains 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
Mzack9999
added
the
Type: Bug
Mzack9999
added
the
Status: Review Needed
ehsandeep
approved these changes
Dec 29, 2021
ehsandeep
added
Status: Completed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
This PR disables, by default, the CNAME record for the web app. The newly introduced flag (
-app-cname) controls the behavior.Reproduction Steps
interactsh-serverwith cname disabled (default behavior):$ sudo go run . -listen-ip 192.168.1.9 -skip-acme -debug -domain example -debuginteractsh-serverwith cname enabled:$ sudo go run . -listen-ip 192.168.1.9 -skip-acme -debug -domain example -debug -app-cname