Support for lighttpd 1.4.36

[ghost]

Hi,

First of all, I want to thank you for your work on mod_websocket. Our application uses WebSockets and (thanks to this module) we didn't have to switch to another web server.

I understand that new version of lighty was released a week ago but could you please tell me if there is an official support for 1.4.36?

Thank you in advance.

[nori0428]

Hi iatsiuk,
Thank you for your comment and sorry for late reply.

But I'm sorry, I have no time to check with latest version.
So please try makepatch.sh as follows.

1. cd /path/to/mod_websocket/contrib/lighttpd1.4
2. git checkout master; git pull; git checkout lighttpd-1.4.36
3. cd /path/to/mod_websocket
4. makepatch.sh

When created patches into pathces/lighttpd-1.4.36, mod_websocket will work correctly with lighttpd-1.4.36.(but not sure)
If some ploblems are occurred, please contact me again.

Regards.

[nori0428]

And also refer to #44

there is an official support for 1.4.36?

What 'official' means? I do not intend to take any responsibility.
Of course, I make efforts to stabilize this module;)

[ghost]

I followed your recommendations and got some alerts about mod_websocket during the compilation. Lighty webserver start is interrupting with the following errors:

2015-08-17 19:02:27: (plugin.c.170) dlopen() failed for: /opt/lighttpd/lib/mod_websocket.so /opt/lighttpd/lib/mod_websocket.so: undefined symbol: chunkqueue_get_append_buffer
2015-08-17 19:02:27: (server.c.679) loading plugins finally failed

Lighttpd developers warns that new release may break old plugins. Thats why I'm asking question about 'official' support.

[nori0428]

I'm very sorry to late reply.I'm very busy to produce this.

And thank you to inform me lighttpd's warn.I'll fix in near future.

[piloos]

Hi,
First of all, thanks for providing this websocket addition to lighttpd.
Since the refactoring done in lighttpd v1.4.36, it is no longer possible to build mod_websocket (like iatsiuk pointed out).
Are there plans to align mod_websocket with the newer versions of lighttpd?
Regards

PS: Do you know why websocket proxying isn't supported by lighttpd by default?

[nori0428]

Hi,
Aleksey.

First of all, sorry for the inconvenience for lacking patches for new
versions of lighttpd.
Now I have no time to maintain this module.

But fortunately, I receive patches from other hacker recently.
So I'll create an issue and attach them after sending this e-mail.
Please try it.

And I don't know about not existing websocket proxy module by default,
sorry.
PS: I use nginx mainly now...😓

Regars,
nori.

2016-04-12 16:37 GMT+09:00 piloos notifications@github.com:

Hi,
First of all, thanks for providing this websocket addition to lighttpd.
Since the refactoring done in lighttpd v1.4.36, it is no longer possible
to build mod_websocket (like iatsiuk pointed out).
Are there plans to align mod_websocket with the newer versions of lighttpd?
Regards

PS: Do you know why websocket proxying isn't supported by lighttpd by
default?

—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
#45 (comment)

[NorioKobota]

Please try this patch for a while.

[piloos]

Thanks. I will give this a try.