-
Notifications
You must be signed in to change notification settings - Fork 138
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
Authentication protected app issue #6
Comments
Probably not, here's the relevant lines: https://github.com/schneems/derailed_benchmarks/blob/master/lib/derailed_benchmarks/tasks.rb#L62 and https://github.com/schneems/derailed_benchmarks/blob/master/lib/derailed_benchmarks/tasks.rb#L57 I added that because i was making a ton of requests to a bad URL by accident. Guess any 2xx request should be considered success. After that, we can't really assume. Maybe make it user-set-able. How does something like that sound to you?
|
That feels weirdly specific for what this gem is trying to do, maybe? Should benchmarking know about acceptable status codes? What if I could just provide some sort of environment variable like IGNORE_BAD_REQUEST=1 . |
Related to #10 |
You can now perform some benchmarking without having to boot your app. Check the readme for more info. I still haven't addressed this specific issue. Not 100% sure the best way to move forwards |
You can test with an authenticated endpoint now. |
I have an application where the root path is a page with omniauth-crowd authentication. Because of this, call_app fails with
Should it really consider a redirect a failure?
The text was updated successfully, but these errors were encountered: