Closed
Bug 800439
Opened 13 years ago
Closed 12 years ago
Stage Squid Change to allow for larger /.well-known/browserid responses
Categories
(Cloud Services :: Operations: Deployment Requests - DEPRECATED, task)
Cloud Services
Operations: Deployment Requests - DEPRECATED
x86_64
Linux
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: ozten, Unassigned)
Details
According to https://github.com/mozilla/browserid/issues/2559 it sounds like we impose a limit to the size of responses when we're fetching /.well-known/browserid during discovery.
1) What is the current value?
2) What is a new sane value? I propose 10x our current value.
We need this deployed to stage, we'll test, and then we'll file a new bug for production deployment.
We should do this soon, outside of our normal train schedule as it's low risk and an operational task against Squid.
Comment 1•12 years ago
|
||
bumped into this looking for something else. ozten, is this still what needs to be done?
Comment 2•12 years ago
|
||
gene, can you verify we can accept large well knowns in Persona production stack?
Comment 3•12 years ago
|
||
We currently limit at 2KB for some reason :
https://github.com/mozilla/identity-ops/blob/master/chef/cookbooks/persona-proxy/templates/default/etc/squid/squid.conf.erb#L88
I can either remove that limit or change it. What would you prefer?
Flags: needinfo?(ozten)
Comment 4•12 years ago
|
||
Let's make sure it's set to max of 10k.
Comment 5•12 years ago
|
||
Change made in physical stage and prod at sysadmins r63883 and in AWS at https://github.com/mozilla/identity-ops/commit/04181aab43b36fa38baa25094868710612220ab8
Change deployed to physical production (both datacenters) physical stage and aws stage
Status: NEW → RESOLVED
Closed: 12 years ago
Flags: needinfo?(ozten)
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•