Please sign in to comment.
Add workaround for 502's on bad `gem push`
If we return a 401 without reading the request body (ie, bad API token) then apache gets confused and shows the user a 502. So we have to be sure to read the body even if we don't need it.
- Loading branch information...
Showing with 7 additions and 0 deletions.