-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Integrating FastCGI into uhttpd: A Request for Support from OpenWrt Developers #12
Comments
You better to ask in the devlist https://lists.infradead.org/mailman/listinfo/openwrt-devel I'm not an OpenWrt developer but I'm skeptical on this. The uhttpd started as a replacement for the BusyBox httpd to support TLS/HTTPS and native Lua execution. Now routers become more powerful and the project is not really needed because you can use the Lighttpd or even Nginx. Today router manufactures use the Lighttpd instead of the uhttpd. The FastCGI is implemented there and actually this is not so difficult thing in less that 600 lines: You may try to reuse the code but it has a different license that may be problematic. |
Thank you for your help and answers. I don’t have high hopes, but seeing that mod_fastcgi.c is only some lines of code, integrating it shouldn’t be too difficult. My main concern is that I have a project focused on reducing the image size, and I hope to make it small enough to free up more usable space for running other applications on the SoC. Currently, it seems that Lighttpd is still too large, so I will attempt the porting. By the way, thank you for informing me that this repo is a mirror; I have since migrated to https://lists.infradead.org/mailman/listinfo/openwrt-devel to request more help. Thank you very much! |
In what ways is lighttpd "too large"? For example: uhttpd does not support HTTP/2. If you want to compare lighttpd and uhttpd sizes, you can disable HTTP/2 support in lighttpd (resulting in a smaller lighttpd memory footprint at runtime) with lighttpd.conf Another example: if you're using TLS, uhttpd uses mbedtls. lighttpd supports multiple TLS libraries. Make sure you are using lighttpd mod_mbedtls to compare with uhttpd. The defaults in lighttpd is to use lighttpd mod_openssl, which can be much faster, but uses much more memory than lighttpd mod_mbedtls. |
I need to port FastCGI to uhttpd or migrate mod_fastcgi.c from Lighttpd into uhttpd. I would like to consult the OpenWrt development team for possible solutions regarding this matter. We look forward to your help and support. Thank you so much!
The text was updated successfully, but these errors were encountered: