Cookie size in uWSGI

If you’re working to ensure your web application can tolerate more and bigger cookies (see my earlier post on cookie size in Nginx), you have to do it across your entire stack. I forgot to do this previously for my uWSGI application, and so today experienced a 502 Bad Gateway error because the cookies exceeded the default limit of 4kB.

I updated my uwsgi.ini file to add this statement:

buffer-size = 65536

 

Hit List

IBM’s Verse email solution has a feature that dynamically displays your most frequently emailed contacts.

I call it my “chain letter hit list.” If I were going to send a chain letter, these are the folks that would receive it:

hitlist2

As you may have guessed from recent posts, my job responsibilities have shifted from a focus on PureApplication to a focus on IBM’s Cloud for VMware solutions. My “hit list” has also shifted to this new group of folks that I’m privileged and excited to work with.

Oh, and I promise not to send anyone a chain letter.

Cookie size in nginx

I find in the age of corporate single sign-on and the multiplication of web applications and services, that more and more frequently I am running into server-side limits on cookie size. All of these servers and services are polluting my browser with their cookie crumbs. This results in web applications returning a 400 error due to header or cookie size limits.

While many web applications are beyond my control, I am taking the time to adjust my own servers so that they can accommodate these growing cookies. For nginx I’ve made the following adjustment to the server clause in my nginx configuration:

server {
  large_client_header_buffers 8 64k;
  client_header_buffer_size 64k;
  . . .
}