Skip to content
Discussion options

You must be logged in to vote

Hi!

DisableLocalhostProtection will stay as a option, where the developer would like to opt out of the protections while understanding the security implications. What will be removed is the MCPGODEBUG parameter that affects the default behavior – in v1.6.0 the default will be for the protection to be enabled.

This means that for some time there will be two options to disable the protections – the DisableLocalhostProtection and MCPGODEBUG. The former is more future proof and if you can, you should use that one. MCPGODEBUG was only introduced for people that are affected by the default behavior change, but changing the source code within their development/release processes will take some ti…

Replies: 1 comment 1 reply

Comment options

You must be logged in to vote
1 reply
@rahul-netizen
Comment options

Answer selected by maciej-kisiel
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants