There is a problem in the existing Glossary HREF handler where passing the language with unexpected casing (e.g. "english" or "spanish" instead of "English" or "Spanish") causes the unprocessed language value to be passed to the glossary API.
Additionally, the handler should exit gracefully (no unhandled exceptions) when the API returns an unexpected status code.
There is a problem in the existing Glossary HREF handler where passing the language with unexpected casing (e.g. "english" or "spanish" instead of "English" or "Spanish") causes the unprocessed language value to be passed to the glossary API.
Additionally, the handler should exit gracefully (no unhandled exceptions) when the API returns an unexpected status code.
Parent Issue: #9999
Sub-Tasks
Notes