search

mozilla / parsys

Participation Systems Issue Tracker
Mozilla Public License 2.0
0 stars 3 forks source link

Investigate Mozillians API clients that can't handle SNI #79

Open flamingspaz opened 7 years ago

flamingspaz commented 7 years ago
yalam96: random note, some mozillians API clients are (as of last year) incapable of speaking SNI over TLS so when you absorb the site, if you're using an SNI-dependent load balancer, they will all break there are clear FAQs all over the internet about fixing python SNI issues, virtually all of which summarize as "switch your code to use the requests module" if that comes up after your migration, fyi in advance :)
floatingatoll commented 7 years ago

We diagnose this now and again for various sites. In short, it's all instances of old Python 2.6 deployments. The clean fix is to update the application code to use the 'requests' module, and if that doesn't help, to update the env's 'requests' module to a newer version with SNI support. (The latest on pypi would work; vendor-provided packages may or may not work, depending on backports.)

On Thu, Mar 9, 2017 at 11:35 AM, Yousef Alam notifications@github.com wrote:

yalam96: random note, some mozillians API clients are (as of last year) incapable of speaking SNI over TLS so when you absorb the site, if you're using an SNI-dependent load balancer, they will all break there are clear FAQs all over the internet about fixing python SNI issues, virtually all of which summarize as "switch your code to use the requests module" if that comes up after your migration, fyi in advance :)

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/mozilla/parsys/issues/79, or mute the thread https://github.com/notifications/unsubscribe-auth/AAFqDDIv-NoRlx2QdlzPPnKnkn-bR2bhks5rkFSFgaJpZM4MYiBe .