Skip to content
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.

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

Production readiness #106

Open
fifarafa opened this issue Feb 28, 2019 · 1 comment
Open

Production readiness #106

fifarafa opened this issue Feb 28, 2019 · 1 comment

Comments

@fifarafa
Copy link

I've a question regarding readme excerpt:

Here is an example of how you can use spew.Sdump() to help debug a web application. Please be sure to wrap your output using the html.EscapeString() function for safety reasons. You should also only use this debugging technique in a development environment, never in production.

What does it mean, why it shouldn't be used in production? Why?

@jrick
Copy link
Contributor

jrick commented Feb 28, 2019

Spew requires unsafe (for all features, a safe version can be compiled with -tags safe) and memory/type safety is not guaranteed in all future Go releases. An upgrade to Go could introduce a security flaw in any application using spew.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants