Bug #6537
closedEntering a very large number for idle_timeout is unchecked, crashes UI
Description
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1113349
Description of problem:
Idle timeouts can be distracting. Thus, uf a user enters a very large number in the config settings for idle_timeout, there is no bounds testing and the UI crashes.
Version-Release number of selected component (if applicable):
Satellite-6.0.3-RHEL-6-20140625.0
How reproducible:
Steps to Reproduce:
1. In config settings, change the idle_timeout value to something large like "9999999"
2. Begin navigating elsewhere in UI.
3. View results
Actual results:
We're sorry, but something went wrong.
We've been notified about this issue and we'll take a look at it shortly.
In production.log
ArgumentError (year too big to marshal: 192146 UTC):
/usr/lib/ruby/gems/1.8/gems/passenger-4.0.18/lib/phusion_passenger/rack/thread_handler_extension.rb:77:in `process_request'
/usr/lib/ruby/gems/1.8/gems/passenger-4.0.18/lib/phusion_passenger/request_handler/thread_handler.rb:140:in `accept_and_process_next_request'
/usr/lib/ruby/gems/1.8/gems/passenger-4.0.18/lib/phusion_passenger/request_handler/thread_handler.rb:108:in `main_loop'
/usr/lib/ruby/gems/1.8/gems/passenger-4.0.18/lib/phusion_passenger/request_handler.rb:441:in `block (3 levels) in start_threads'
Expected results:
Sane bounds testing of this field (and all others!).
Additional info:
Updated by Dominic Cleal about 10 years ago
- Status changed from New to Assigned
- Target version set to 1.8.0
Updated by Ori Rabin about 10 years ago
- Status changed from Assigned to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/1582 added
- Pull request deleted (
)
Updated by Ori Rabin about 10 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset 8e5a869a80fe588fb3b228e74951c30713abc030.
Updated by Dominic Cleal about 10 years ago
- Translation missing: en.field_release set to 10
Updated by Dominic Cleal almost 10 years ago
- Related to Bug #7579: Session reset after each page request, idle_timeout set to zero added