# Yahoo login for Discourse

**URL:** https://meta.discourse.org/t/yahoo-login-for-discourse/74060
**Category:** Bug
**Created:** [14 Novembro , 2017 16:20 UTC](https://meta.discourse.org/t/yahoo-login-for-discourse/74060 "2017-11-14T16:20:47Z")
**Posts on this page:** 1
**Showing post:** 15

<div class="post-metadata">

### Author: ![supermathie](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/supermathie/32/507518_2.png) [@supermathie](https://meta.discourse.org/u/supermathie)
#### Post date: [16 Novembro , 2017 18:26 UTC](https://meta.discourse.org/t/yahoo-login-for-discourse/74060/15 "2017-11-16T18:26:28Z")

</div>

> [@Neil\_Brooks2](#):
>
> Its a site that is hosted with you. does that make a difference?

It does make a difference, actually.

The actual problem was that in our environment the size of the headers sent back by Discourse for the request going to /auth/yahoo are very large - 3897 bytes.

BUT when navigating around before trying to login, the headers (one of which is the cookie that has some pre-login session state) gets larger, e.g. up to a size of 4142 bytes. This is larger than the [buffer which nginx allocates](http://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_buffer_size) for holding that first part of the response.

Upping the size of `proxy_buffer_size` to 8k was necessary for our infrastructure and has solved the problem on [try.discourse.org](http://try.discourse.org).

@Neil_Brooks2, please let me know (in a PM) which sites are yours and I will ensure those are deployed next, we can continue testing there and then we’ll roll out the change to everyone.

---

_[View the full topic](https://meta.discourse.org/t/yahoo-login-for-discourse/74060)._