On Thursday, September 28, 2017 at 4:33:27 PM UTC-7, Dave S wrote: > > > [...] > I did an experiment with going back to http (no-ess) so that I could read > the frames in tcpdump, and I see that the client is getting the > Content-Length header in (and it appears to this Mk I eyeball to be > correct). This experiment was with the nginx front-end, and I only > captured the client side (because I specified the port in the tcpdump > command). After what appears to be the last byte of the data, which is the > last byte of the hex dump for that frame, there are 2 4500 0028 frames as > the final handshake. > > It may be a couple of days before I can repeat the experiment with Rocket > getting the no-ess data. > > > Got the test started, but it was running very slowly (like brief activity -- a chunk? -- every 10 minutes), and I decided to head for home. I'll see what came of it in the morning.
> >> >> >>> BTW, when uwsgi calls web2py, it seems to be starting a new >>> logs/web2py.log (rotating the old ones). Is there a way to have it >>> continue to use the currently open one? I'm not yet using --emperor; is >>> that part of the issue? >>> >>> > Lots of one-line log files is a bit annoying. > > This seems to have been from competing file-opens. I've worked around it by not having the two engines log to the same place; in this case, by having a separate copy of web2py and its subdirs. There doesn't seem to be a web2py command line option for specifying an alternate logging location, so I went for an alternative whole-kit-and-kaboodle. /dps -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
