#69880 did not work and we continue to see about 300 student requests fail each day due to connectivity issues with WebPurify.

This is occuring, in part, because of a latent defect in our invocation of Net::HTTP.start. We failed to add the splat (**) operator to the final CONNECTION_OPTIONS hash argument, so since upgrading to Ruby 3.x, we've been incorrectly passing it to the 3rd argument (p_addr http proxy address) https://docs.ruby-lang.org/en/3.1/Net/HTTP.html#method-c-start

Also switch to HTTPS (TLS) because we've been gifted an Enterprise license and that supports SSL and connectivity may be more reliable over HTTPS and port 443.

Testing story

Configured local development environment with an API key and manually executed many of the unit tests (which use VCR to mock interactions with the WebPurify webservice):

[development] dashboard > require 'cdo/web_purify'
=> false
[development] dashboard > WebPurify.find_potential_profanities('not a swear')
=> nil
[development] dashboard > WebPurify.find_potential_profanities('assuage')
=> nil
[development] dashboard > WebPurify.find_potential_profanities('8005555555 t')
=> nil
[development] dashboard > WebPurify.find_potential_profanities('sh1t! holy shit')
=> ["sh1t", "shit"]
[development] dashboard > WebPurify.find_potential_profanities('shitstain')
=> ["shitstain"]
[development] dashboard > WebPurify.find_potential_profanities('ass')
=> ["ass"]
[development] dashboard > WebPurify.find_potential_profanities('scheiße', ['de'])
=> ["scheiße"]
[development] dashboard > WebPurify.find_potential_profanities('puta madre', ['es'])
=> ["puta"]
[development] dashboard > WebPurify.find_potential_profanities('some mierda and some scheiße', ['es', 'de'])
=> ["mierda", "scheiße"]

Deployment strategy

Follow-up work

Implement HTTP retry for the cases where the HTTP connection pool gives us a stale connection (if we set keep-alive > 0), and for cases when the webservice has other types of connectivity errors).

Privacy

Security

Caching

PR Creation Checklist:

• Tests provide adequate coverage
• Privacy impacts have been documented
• Security impacts have been documented
• Code is well-commented
• New features are translatable or updates will not break translations
• Relevant documentation has been added or updated
• User impact is well-understood and desirable
• Follow-up work items (including potential tech debt) are tracked and linked