Bullettrace in profiler.

[HelloGrayson]

Wondering about the possibility of allowing profiler to be temporarily turned on by headers configured when instantiating the middleware. This would allow people to capture profiles in production.

Some ideas:

# enable profile for this request
curl myapp.com -H X-Werkzeug-Profiling-Enabled:1

# enable profile, emailing to me@myspace.com
curl myapp.com -H X-Werkzeug-Profiling-Enabled -H X-Werkzeug-Profiling-Email-To:me@myspace.com 

# profile and write to my home dir
curl myapp.com -H  X-Werkzeug-Profiling-Enabled:1 -H X-Werkzeug-Profiling-Write-To:/home/me/profs

Thoughts?

[untitaker]

I'd implement these header features in a subclass of the original profiler middleware. However, much of contrib (including the profiler itself) is already out-of-scope for Werkzeug, see #4. Maybe it still could stay in Werkzeug (because it's a useful WSGI middleware), i don't know.

[HelloGrayson]

I see. Potentially I could just create a standalone python package containing a WSGI middleware. Doesn't look like I need anything specific to Werkzeug even. Thanks @untitaker

[untitaker]

The whole contrib stuff could be packaged separately, there is AFAIK nothing that couples them. If you are interested, you could build your own standalone WSGI profiler forked from Werkzeug and for version 1.0 we'll deprecate Werkzeug's in favour of yours.