Skip to content
This repository was archived by the owner on Feb 6, 2024. It is now read-only.

Conversation

@adamthehutt
Copy link

We're using CAS in gateway mode and are experiencing errors when the original URL of the client application includes invalid UTF-8 characters. These are not "legitimate" user requests, but they happen a lot so it would be nice to prevent the error reports.

Here's part of a backtrace:

activesupport-3.2.19/lib/active_support/core_ext/object/blank.rb:105→ =~
activesupport-3.2.19/lib/active_support/core_ext/object/blank.rb:105→ !~
activesupport-3.2.19/lib/active_support/core_ext/object/blank.rb:105→ blank?
casino-2.0.4/app/processors/casino/processor_concern/service_tickets.rb:30→ clean_service_url
casino-2.0.4/app/processors/casino/login_credential_requestor_processor.rb:54→ check_service_allowed
casino-2.0.4/app/processors/casino/login_credential_requestor_processor.rb:22→ process
casino-2.0.4/app/controllers/casino/sessions_controller.rb:10→ new

@coveralls
Copy link

Coverage Status

Coverage increased (+0.0%) when pulling 6603eaa on fracturedatlas:master into 23b005a on rbCAS:master.

@pencil
Copy link
Member

pencil commented Jul 26, 2014

Thank you! Do you happen to have an example URL that triggers the actual problem?

@adamthehutt
Copy link
Author

Here's an example of recent one, but it looks like the non UTF-8 character has already been scrubbed here (this is from the Errbit report):

https://cas.fracturedatlas.org?service=http%3A%2F%2Fwww.fracturedatlas.org%2Findex.php%3Fdo%3Durl%26%FFcs&gateway=true

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants