Hawk777
- Login: Hawk777
- Registered on: 2011-12-22
- Last sign in: 2024-01-21
Issues
open | closed | Total | |
---|---|---|---|
Assigned issues | 0 | 0 | 0 |
Reported issues | 0 | 3 | 3 |
Activity
2024-01-21
- 19:58 Lighttpd Bug #3239: syslog level set to error for messages that are not errors
- Thank you for that change.
- 18:17 Lighttpd Bug #3239: syslog level set to error for messages that are not errors
- > You have not identified a specific error message or messages which bother you (besides those behind debug directive...
2024-01-19
- 01:44 Lighttpd Bug #3239: syslog level set to error for messages that are not errors
- > How would you like to be credited in the commit? 'Hawk777' or something else? I typically add a "(thx Hawk777)" in ...
2024-01-08
- 06:38 Lighttpd Bug #3239: syslog level set to error for messages that are not errors
- Great, here’s a patch for three of the five calls to `log_error_multiline`. They’re all controlled by config directiv...
2024-01-05
- 06:54 Lighttpd Bug #3239: syslog level set to error for messages that are not errors
- > If you find the time and have the inclination, you're welcome to submit patches for discussion which update various...
2023-12-31
- 21:03 Lighttpd Support: RE: [Solved] Websocket-supporting backends
- Well, if you’ve already implemented it, then the discussion about specifications is no longer relevant. Thank you for...
- 20:40 Lighttpd Bug #3239: syslog level set to error for messages that are not errors
- > Therefore, while you are correct that this is a limitation in lighttpd, I may end up closing this issue as "Won't F...
2023-12-30
- 20:43 Lighttpd Bug #3239 (Fixed): syslog level set to error for messages that are not errors
- The message “server started (lighttpd/versionnumber)” is not an error, but it gets sent to syslog at LOG_ERR level. I...
2023-12-01
- 04:19 Lighttpd Support: RE: Websocket-supporting backends
- > The SCGI specification requires CONTENT_LENGTH as the very first request header in the SCGI request.
>
> There a...
2023-11-30
- Hi,
From reading the documentation, I believe I understand that the only ways of handling websockets are mod_proxy, ...
Also available in: Atom