Re: [go-nuts] How to deal with "Expect: 100-continue" *without* sending a 100 status

2016-10-29 Thread jrwren
Sorry to resurrect a month old thread, but I just implemented bullet #2 with this patch. I need to disable the automatic 100-continue behavior so that my handler can reply with a 40X status before the client read the 100-contine and starts sending data. On Saturday, September 17, 2016 at 12:

Re: [go-nuts] How to deal with "Expect: 100-continue" *without* sending a 100 status

2016-09-17 Thread Ian Rose
Thanks Dave - all good suggestions! > Use a GCE Network LB instead of HTTP LB. I'm hoping to avoid using a network LB since we are operating over https so that means we'll have to terminate SSL ourselves (which means distributing our certs to each backend instance). Using an http(s) LB means we

Re: [go-nuts] How to deal with "Expect: 100-continue" *without* sending a 100 status

2016-09-16 Thread David Anderson
Tricky one. A couple of options spring to mind, none of them amazingly good: - Use a GCE Network LB instead of HTTP LB. You can bring the TCP sessions straight to your web servers, with load-balancing done per-TCP-session rather than per-HTTP-request. - Build your web server using a mo