chuigda / chttpd

Toy HTTP server implementation, with tons of toys used

⚠️Warning⚠️: This user's profile may include the following contents:

• Ancient Technology
• Native Language Fundamentalism
• Racket YYDS
• Anti-Fans
• Pigeon
• unsafe impl !PoliticalRight for Me {}
• Sweating Soybean
• Rocket Building
• Military race
• Hyperblunderemia
• Socialism/Communism/Sovietskiy
• Orange juice 🍹

If you fell uncomfortable, please adapt as soon as possible😜

About Chuigda WhiteGive

• 🔭 I’m currently working on Project-WGX and Project-602.
• 🌱 I’m currently learning Computer Graphics, Vulkan, Chess and many funny things.
• 😄 Pronouns: He/Him
• 📫 How to reach me:
  • Personal website: self.icey.tech
  • Email: [email protected]
• ⚡ Fun fact: My nickname "Chuigda" comes from this file name.
  • "Chui" stands for hammer or mallet in Chinese
  • "gda" comes from Agda

chttpd's Issues

Benchmarking

Testing platform: x86 alpine, linux kernel 5.10

Performance

Caching support

Caching is not indeed necessary, but will improve the experience of users and performance of CDNs by alot. Here is a piece of documentation on it.

Support "no-value" query parameters

chttpd should support "no-value" query parameters like:
?option1&option2
Which should be parsed to

{
    "option1": null,
    "option2": null
}

By this time chttpd refuses this pattern.

Unify response representation

By this time, responses come in two different forms:

• for intern and static handlers, responses are directly written to the file stream
• for dcgi handlers, responses are created by DCGI libraries, saved in a temporary location, and then written to the file stream

Having two different modes makes it hard for us to implement filters/interceptors. It would be nice to unify all these things.

Simplest wildcard support

By this time the routes are appointed explicitly one by one. We want some wildcard things, so that we can serve static files easier.

Support "OPTION" request

Without OPTION request, CORS will be impossible. This can be solved somewhere else, however.

Windows support

Recently, we need to deploy a local CI with chttpd on a Windows server. Though it is possible to use MSYS or Cygwin yet, we still prefer native implementations.

Dynamic library preloading & caching

Till now, dynamic libraries are loaded in some "on demand" mode. The HTTP handler loads the requested dynamic library before handling every request, and unload it after. This may reduce performance and limit the functionality of external dynamic libraries somehow.