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

puma should not display exception/backtrace in production #256

Closed
rkh opened this issue May 13, 2013 · 6 comments
Closed

puma should not display exception/backtrace in production #256

rkh opened this issue May 13, 2013 · 6 comments

Comments

@rkh
Copy link
Contributor

rkh commented May 13, 2013

No description provided.

@bnorton
Copy link

bnorton commented May 20, 2013

I'm not seeing this happen. What version and are you using -e production when starting puma?

@rkh
Copy link
Contributor Author

rkh commented May 20, 2013

RACK_ENV=puma rackup .... Try running with /?a=1&a%5Ba%5D=1 as path.

@rkh
Copy link
Contributor Author

rkh commented May 20, 2013

Ah, we're on an outdated puma.

@mkwiatkowski
Copy link

This should be closed then?

@rkh
Copy link
Contributor Author

rkh commented Jun 19, 2013

Still seeing this with Puma 2.1.0

run proc { |env|
  [307,
    {'Location' => '/?a=1&a%5Ba%5D=1', 'Content-Type' => 'text/plain'},
    [Rack::Request.new(env).params.inpect]]
}

Ran with rackup -s puma -E production.

image

@evanphx evanphx closed this as completed in a99a3f0 Jul 1, 2013
@rkh
Copy link
Contributor Author

rkh commented Jul 1, 2013

<3

MSP-Greg added a commit to MSP-Greg/puma that referenced this issue Jul 30, 2020
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

3 participants