> On Aug 22, 2016, at 23:33, [email protected] wrote:
>> My ini configuration specifies:
>>
>>    log-date = %%Y-%%m-%%d %%H:%%M:%%S
>>    logformat-strftime = true
>>
>>
>> When uWSGI logs non-request-related messages, it uses the specified date
>> format, e.g.
>>
>>    2016-08-22 00:00:04 - *** Starting uWSGI 2.0.13.1 (64bit) on [Mon Aug
>> 22 00:00:04 2016] ***
>>
>>
>> I wanted uWSGI to use this format when logging HTTP requests too.
>> Accomplishing this was simply a matter of adding %(date) inside the
>> "log-format" string.
>
>
> Actually this isn't working for requests uWSGI is serving for my
> static-map rule, so I had to switch back to using %(ltime) for now. Is
> there any interest from uWSGI developers in making %(date) work as
> described above here?



unless completely broken, risky or useless, we are genrally open to pull
requests. Logchunks are pretty easy to add:

add your new chunk here:

https://github.com/unbit/uwsgi/blob/master/core/logging.c#L1953

and implement its feature in a uwsgi_lf_[chunkname] function:

https://github.com/unbit/uwsgi/blob/master/core/logging.c#L1090


You can define them in plugins too, but something like date matching could
be absolutely exposed in core

>
>> Question: To keep things simpler on my server, I have uWSGI listening on
>> port 8443 with packets from port 443 forwarding to it. Given that I'm
>> adding appropriate cache headers and have CloudFlare in front to absorb
>> traffic, and that I have uWSGI's "https2" and "static-map" functionality
>> configured and working fine, I saw no need to add something like NGINX
>> in front of uWSGI to handle HTTPS or static file serving.
>>
>> Is a setup like this unusual or ill-advised for some reason? It's been
>> working well for me so far, but it's only been a few months of
>> development/test traffic; I have not yet put this behind production
>> traffic.
>
>
> Is anyone on this list able to offer any feedback on this?
>
>


there is nothing wrong in this setup and it is pretty common unless you
need some nginx (or whatever) webserver feature. The uWSGI http router is
solid, but pretty basic (but has some interesting feature like dynamic
registration of ssl certificates)

--
Roberto De Ioris
http://unbit.com
_______________________________________________
uWSGI mailing list
[email protected]
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi

Reply via email to