In the previous article I explained how modules of all types link into Nginx. Now let’s look closer at the specifics of HTTP modules.
An HTTP module has the value NGX_HTTP_MODULE in its type field and the ctx field points to a global instance of a structure ngx_http_module_t: Continue reading
In previous articles I have deliberately omitted almost everything related to the question of linking your module with Nginx. It is important, however, that you know about it.
Let’s take a closer look at the metainformation that your module must contain, so that Nginx can initialise and configure it. Continue reading
Let’s start with declaring a structure that will contain configuration of our module: Continue reading
Let’s see what we need to do in order to return a simple page to a client using Nginx module. We need to generate a header and a body of the response. To send a response header we use function ngx_http_send_header:
ngx_int_t ngx_http_send_header(ngx_http_request_t *r);
The only argument r is the request for which you want to generate and send a header. This function serializes headers from the list of response headers r->headers_out into a buffer and sends this buffer to a client or queues this buffer into output queue r->out if the client socket is not writeable. The HTTP version in the status line will be determined for you automatically. The HTTP status code is taken from r->headers_out.status and the status text will be filled according to the status code.
Lets see how we can add some custom header line to our response header. Continue reading
Nginx processes HTTP requests in multiple phases. In each of the phases there might be 0 or more handlers called. In the Nginx source code phases have specific constants associated with them. Here is a list of all phases:
- NGX_HTTP_SERVER_REWRITE_PHASE — the phase of request URI transformation on virtual server level;
- NGX_HTTP_FIND_CONFIG_PHASE — the phase of configuration location lookup;
- NGX_HTTP_REWRITE_PHASE — the phase of request URI transformation on location level;
- NGX_HTTP_POST_REWRITE_PHASE — request URI transformation post-processing phase;
- NGX_HTTP_PREACCESS_PHASE — access restrictions check preprocessing phase;
- NGX_HTTP_ACCESS_PHASE — access restrictions check phase;
- NGX_HTTP_POST_ACCESS_PHASE — access restrictions check post-processing phase;
- NGX_HTTP_TRY_FILES_PHASE — try_files directive processing phase;
- NGX_HTTP_CONTENT_PHASE — content generation phase;
- NGX_HTTP_LOG_PHASE — logging phase.
On every phase you can register any number of your handlers. Continue reading