1 /* Licensed to the Apache Software Foundation (ASF) under one or more
2 * contributor license agreements. See the NOTICE file distributed with
3 * this work for additional information regarding copyright ownership.
4 * The ASF licenses this file to You under the Apache License, Version 2.0
5 * (the "License"); you may not use this file except in compliance with
6 * the License. You may obtain a copy of the License at
8 * http://www.apache.org/licenses/LICENSE-2.0
10 * Unless required by applicable law or agreed to in writing, software
11 * distributed under the License is distributed on an "AS IS" BASIS,
12 * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
13 * See the License for the specific language governing permissions and
14 * limitations under the License.
19 * @brief Apache filter library
26 #include "apr_buckets.h"
39 * @brief input filtering modes
42 /** The filter should return at most readbytes data. */
44 /** The filter should return at most one line of CRLF data.
45 * (If a potential line is too long or no CRLF is found, the
46 * filter may return partial data).
49 /** The filter should implicitly eat any CRLF pairs that it sees. */
51 /** The filter read should be treated as speculative and any returned
52 * data should be stored for later retrieval in another mode. */
54 /** The filter read should be exhaustive and read until it can not
56 * Use this mode with extreme caution.
59 /** The filter should initialize the connection if needed,
60 * NNTP or FTP over SSL for example.
66 * @defgroup APACHE_CORE_FILTER Filter Chain
67 * @ingroup APACHE_CORE
69 * Filters operate using a "chaining" mechanism. The filters are chained
70 * together into a sequence. When output is generated, it is passed through
71 * each of the filters on this chain, until it reaches the end (or "bottom")
72 * and is placed onto the network.
74 * The top of the chain, the code generating the output, is typically called
75 * a "content generator." The content generator's output is fed into the
76 * filter chain using the standard Apache output mechanisms: ap_rputs(),
77 * ap_rprintf(), ap_rwrite(), etc.
79 * Each filter is defined by a callback. This callback takes the output from
80 * the previous filter (or the content generator if there is no previous
81 * filter), operates on it, and passes the result to the next filter in the
82 * chain. This pass-off is performed using the ap_fc_* functions, such as
83 * ap_fc_puts(), ap_fc_printf(), ap_fc_write(), etc.
85 * When content generation is complete, the system will pass an "end of
86 * stream" marker into the filter chain. The filters will use this to flush
87 * out any internal state and to detect incomplete syntax (for example, an
88 * unterminated SSI directive).
93 /* forward declare the filter type */
94 typedef struct ap_filter_t ap_filter_t;
97 * @name Filter callbacks
99 * This function type is used for filter callbacks. It will be passed a
100 * pointer to "this" filter, and a "bucket brigade" containing the content
103 * In filter->ctx, the callback will find its context. This context is
104 * provided here, so that a filter may be installed multiple times, each
105 * receiving its own per-install context pointer.
107 * Callbacks are associated with a filter definition, which is specified
108 * by name. See ap_register_input_filter() and ap_register_output_filter()
109 * for setting the association between a name for a filter and its
110 * associated callback (and other information).
112 * If the initialization function argument passed to the registration
113 * functions is non-NULL, it will be called iff the filter is in the input
114 * or output filter chains and before any data is generated to allow the
115 * filter to prepare for processing.
117 * The bucket brigade always belongs to the caller, but the filter
118 * is free to use the buckets within it as it sees fit. Normally,
119 * the brigade will be returned empty. Buckets *may not* be retained
120 * between successive calls to the filter unless they have been
121 * "set aside" with a call apr_bucket_setaside. Typically this will
122 * be done with ap_save_brigade(). Buckets removed from the brigade
123 * become the responsibility of the filter, which must arrange for
124 * them to be deleted, either by doing so directly or by inserting
125 * them in a brigade which will subsequently be destroyed.
127 * For the input and output filters, the return value of a filter should be
128 * an APR status value. For the init function, the return value should
129 * be an HTTP error code or OK if it was successful.
134 typedef apr_status_t (*ap_out_filter_func)(ap_filter_t *f,
135 apr_bucket_brigade *b);
136 typedef apr_status_t (*ap_in_filter_func)(ap_filter_t *f,
137 apr_bucket_brigade *b,
138 ap_input_mode_t mode,
139 apr_read_type_e block,
140 apr_off_t readbytes);
141 typedef int (*ap_init_filter_func)(ap_filter_t *f);
143 typedef union ap_filter_func {
144 ap_out_filter_func out_func;
145 ap_in_filter_func in_func;
151 * Filters have different types/classifications. These are used to group
152 * and sort the filters to properly sequence their operation.
154 * The types have a particular sort order, which allows us to insert them
155 * into the filter chain in a determistic order. Within a particular grouping,
156 * the ordering is equivalent to the order of calls to ap_add_*_filter().
159 /** These filters are used to alter the content that is passed through
160 * them. Examples are SSI or PHP. */
161 AP_FTYPE_RESOURCE = 10,
162 /** These filters are used to alter the content as a whole, but after all
163 * AP_FTYPE_RESOURCE filters are executed. These filters should not
164 * change the content-type. An example is deflate. */
165 AP_FTYPE_CONTENT_SET = 20,
166 /** These filters are used to handle the protocol between server and
167 * client. Examples are HTTP and POP. */
168 AP_FTYPE_PROTOCOL = 30,
169 /** These filters implement transport encodings (e.g., chunking). */
170 AP_FTYPE_TRANSCODE = 40,
171 /** These filters will alter the content, but in ways that are
172 * more strongly associated with the connection. Examples are
173 * splitting an HTTP connection into multiple requests and
174 * buffering HTTP responses across multiple requests.
176 * It is important to note that these types of filters are not
177 * allowed in a sub-request. A sub-request's output can certainly
178 * be filtered by ::AP_FTYPE_RESOURCE filters, but all of the "final
179 * processing" is determined by the main request. */
180 AP_FTYPE_CONNECTION = 50,
181 /** These filters don't alter the content. They are responsible for
182 * sending/receiving data to/from the client. */
183 AP_FTYPE_NETWORK = 60
187 * These flags indicate whether the given filter is an input filter or an
193 /** Output filters */
194 AP_FILTER_OUTPUT = 2,
195 } ap_filter_direction_e;
198 * This is the request-time context structure for an installed filter (in
199 * the output filter chain). It provides the callback to use for filtering,
200 * the request this filter is associated with (which is important when
201 * an output chain also includes sub-request filters), the context for this
202 * installed filter, and the filter ordering/chaining fields.
204 * Filter callbacks are free to use ->ctx as they please, to store context
205 * during the filter process. Generally, this is superior over associating
206 * the state directly with the request. A callback should not change any of
210 typedef struct ap_filter_rec_t ap_filter_rec_t;
211 typedef struct ap_filter_provider_t ap_filter_provider_t;
214 * @brief This structure is used for recording information about the
215 * registered filters. It associates a name with the filter's callback
218 * At the moment, these are simply linked in a chain, so a ->next pointer
221 * It is used for any filter that can be inserted in the filter chain.
222 * This may be either a httpd-2.0 filter or a mod_filter harness.
223 * In the latter case it contains dispatch, provider and protocol information.
224 * In the former case, the new fields (from dispatch) are ignored.
226 struct ap_filter_rec_t {
227 /** The registered name for this filter */
230 /** The function to call when this filter is invoked. */
231 ap_filter_func filter_func;
233 /** The function to call directly before the handlers are invoked
234 * for a request. The init function is called once directly
235 * before running the handlers for a request or subrequest. The
236 * init function is never called for a connection filter (with
237 * ftype >= AP_FTYPE_CONNECTION). Any use of this function for
238 * filters for protocols other than HTTP is specified by the
239 * module supported that protocol.
241 ap_init_filter_func filter_init_func;
243 /** The next filter_rec in the list */
244 struct ap_filter_rec_t *next;
246 /** Providers for this filter */
247 ap_filter_provider_t *providers;
249 /** The type of filter, either AP_FTYPE_CONTENT or AP_FTYPE_CONNECTION.
250 * An AP_FTYPE_CONTENT filter modifies the data based on information
251 * found in the content. An AP_FTYPE_CONNECTION filter modifies the
252 * data based on the type of connection.
254 ap_filter_type ftype;
256 /** Trace level for this filter */
259 /** Protocol flags for this filter */
260 unsigned int proto_flags;
262 /** Whether the filter is an input or output filter */
263 ap_filter_direction_e direction;
267 * @brief The representation of a filter chain.
269 * Each request has a list
270 * of these structures which are called in turn to filter the data. Sub
271 * requests get an exact copy of the main requests filter chain.
274 /** The internal representation of this filter. This includes
275 * the filter's name, type, and the actual function pointer.
277 ap_filter_rec_t *frec;
279 /** A place to store any data associated with the current filter */
282 /** The next filter in the chain */
285 /** The request_rec associated with the current filter. If a sub-request
286 * adds filters, then the sub-request is the request associated with the
291 /** The conn_rec associated with the current filter. This is analogous
292 * to the request_rec, except that it is used for connection filters.
296 /** Buffered data associated with the current filter. */
297 apr_bucket_brigade *bb;
299 /** Dedicated pool to use for deferred writes. */
300 apr_pool_t *deferred_pool;
305 * Get the current bucket brigade from the next filter on the filter
306 * stack. The filter returns an apr_status_t value. If the bottom-most
307 * filter doesn't read from the network, then ::AP_NOBODY_READ is returned.
308 * The bucket brigade will be empty when there is nothing left to get.
309 * @param filter The next filter in the chain
310 * @param bucket The current bucket brigade. The original brigade passed
311 * to ap_get_brigade() must be empty.
312 * @param mode The way in which the data should be read
313 * @param block How the operations should be performed
314 * ::APR_BLOCK_READ, ::APR_NONBLOCK_READ
315 * @param readbytes How many bytes to read from the next filter.
317 AP_DECLARE(apr_status_t) ap_get_brigade(ap_filter_t *filter,
318 apr_bucket_brigade *bucket,
319 ap_input_mode_t mode,
320 apr_read_type_e block,
321 apr_off_t readbytes);
324 * Pass the current bucket brigade down to the next filter on the filter
325 * stack. The filter returns an apr_status_t value. If the bottom-most
326 * filter doesn't write to the network, then ::AP_NOBODY_WROTE is returned.
327 * @param filter The next filter in the chain
328 * @param bucket The current bucket brigade
330 * @remark Ownership of the brigade is retained by the caller. On return,
331 * the contents of the brigade are UNDEFINED, and the caller must
332 * either call apr_brigade_cleanup or apr_brigade_destroy on
335 AP_DECLARE(apr_status_t) ap_pass_brigade(ap_filter_t *filter,
336 apr_bucket_brigade *bucket);
339 * Pass the current bucket brigade down to the next filter on the filter
340 * stack checking for filter errors. The filter returns an apr_status_t value.
341 * Returns ::OK if the brigade is successfully passed
342 * ::AP_FILTER_ERROR on a filter error
343 * ::HTTP_INTERNAL_SERVER_ERROR on all other errors
344 * @param r The request rec
345 * @param bucket The current bucket brigade
346 * @param fmt The format string. If NULL defaults to "ap_pass_brigade returned"
347 * @param ... The arguments to use to fill out the format string
348 * @remark Ownership of the brigade is retained by the caller. On return,
349 * the contents of the brigade are UNDEFINED, and the caller must
350 * either call apr_brigade_cleanup or apr_brigade_destroy on
353 AP_DECLARE(apr_status_t) ap_pass_brigade_fchk(request_rec *r,
354 apr_bucket_brigade *bucket,
357 __attribute__((format(printf,3,4)));
360 * This function is used to register an input filter with the system.
361 * After this registration is performed, then a filter may be added
362 * into the filter chain by using ap_add_input_filter() and simply
363 * specifying the name.
365 * @param name The name to attach to the filter function
366 * @param filter_func The filter function to name
367 * @param filter_init The function to call before the filter handlers
369 * @param ftype The type of filter function, either ::AP_FTYPE_CONTENT_SET or
370 * ::AP_FTYPE_CONNECTION
371 * @see add_input_filter()
373 AP_DECLARE(ap_filter_rec_t *) ap_register_input_filter(const char *name,
374 ap_in_filter_func filter_func,
375 ap_init_filter_func filter_init,
376 ap_filter_type ftype);
378 /** @deprecated @see ap_register_output_filter_protocol */
379 AP_DECLARE(ap_filter_rec_t *) ap_register_output_filter(const char *name,
380 ap_out_filter_func filter_func,
381 ap_init_filter_func filter_init,
382 ap_filter_type ftype);
384 /* For httpd-?.? I suggest replacing the above with
385 #define ap_register_output_filter(name,ffunc,init,ftype) \
386 ap_register_output_filter_protocol(name,ffunc,init,ftype,0)
390 * This function is used to register an output filter with the system.
391 * After this registration is performed, then a filter may be added
392 * directly to the filter chain by using ap_add_output_filter() and
393 * simply specifying the name, or as a provider under mod_filter.
395 * @param name The name to attach to the filter function
396 * @param filter_func The filter function to name
397 * @param filter_init The function to call before the filter handlers
399 * @param ftype The type of filter function, either ::AP_FTYPE_CONTENT_SET or
400 * ::AP_FTYPE_CONNECTION
401 * @param proto_flags Protocol flags: logical OR of AP_FILTER_PROTO_* bits
402 * @return the filter rec
403 * @see ap_add_output_filter()
405 AP_DECLARE(ap_filter_rec_t *) ap_register_output_filter_protocol(
407 ap_out_filter_func filter_func,
408 ap_init_filter_func filter_init,
409 ap_filter_type ftype,
410 unsigned int proto_flags);
413 * Adds a named filter into the filter chain on the specified request record.
414 * The filter will be installed with the specified context pointer.
416 * Filters added in this way will always be placed at the end of the filters
417 * that have the same type (thus, the filters have the same order as the
418 * calls to ap_add_filter). If the current filter chain contains filters
419 * from another request, then this filter will be added before those other
422 * To re-iterate that last comment. This function is building a FIFO
423 * list of filters. Take note of that when adding your filter to the chain.
425 * @param name The name of the filter to add
426 * @param ctx Context data to provide to the filter
427 * @param r The request to add this filter for (or NULL if it isn't associated with a request)
428 * @param c The connection to add the fillter for
430 AP_DECLARE(ap_filter_t *) ap_add_input_filter(const char *name, void *ctx,
431 request_rec *r, conn_rec *c);
434 * Variant of ap_add_input_filter() that accepts a registered filter handle
435 * (as returned by ap_register_input_filter()) rather than a filter name
437 * @param f The filter handle to add
438 * @param ctx Context data to provide to the filter
439 * @param r The request to add this filter for (or NULL if it isn't associated with a request)
440 * @param c The connection to add the fillter for
442 AP_DECLARE(ap_filter_t *) ap_add_input_filter_handle(ap_filter_rec_t *f,
448 * Returns the filter handle for use with ap_add_input_filter_handle.
450 * @param name The filter name to look up
452 AP_DECLARE(ap_filter_rec_t *) ap_get_input_filter_handle(const char *name);
455 * Add a filter to the current request. Filters are added in a FIFO manner.
456 * The first filter added will be the first filter called.
457 * @param name The name of the filter to add
458 * @param ctx Context data to set in the filter
459 * @param r The request to add this filter for (or NULL if it isn't associated with a request)
460 * @param c The connection to add this filter for
461 * @note If adding a connection-level output filter (i.e. where the type
462 * is >= AP_FTYPE_CONNECTION) during processing of a request, the request
463 * object r must be passed in to ensure the filter chains are modified
464 * correctly. f->r will still be initialized as NULL in the new filter.
466 AP_DECLARE(ap_filter_t *) ap_add_output_filter(const char *name, void *ctx,
467 request_rec *r, conn_rec *c);
470 * Variant of ap_add_output_filter() that accepts a registered filter handle
471 * (as returned by ap_register_output_filter()) rather than a filter name
473 * @param f The filter handle to add
474 * @param ctx Context data to set in the filter
475 * @param r The request to add this filter for (or NULL if it isn't associated with a request)
476 * @param c The connection to add the filter for
477 * @note If adding a connection-level output filter (i.e. where the type
478 * is >= AP_FTYPE_CONNECTION) during processing of a request, the request
479 * object r must be passed in to ensure the filter chains are modified
480 * correctly. f->r will still be initialized as NULL in the new filter.
482 AP_DECLARE(ap_filter_t *) ap_add_output_filter_handle(ap_filter_rec_t *f,
488 * Returns the filter handle for use with ap_add_output_filter_handle.
490 * @param name The filter name to look up
492 AP_DECLARE(ap_filter_rec_t *) ap_get_output_filter_handle(const char *name);
495 * Remove an input filter from either the request or connection stack
496 * it is associated with.
497 * @param f The filter to remove
500 AP_DECLARE(void) ap_remove_input_filter(ap_filter_t *f);
503 * Remove an output filter from either the request or connection stack
504 * it is associated with.
505 * @param f The filter to remove
508 AP_DECLARE(void) ap_remove_output_filter(ap_filter_t *f);
511 * Remove an input filter from either the request or connection stack
512 * it is associated with.
513 * @param next The filter stack to search
514 * @param handle The filter handle (name) to remove
515 * @return APR_SUCCESS on removal or error
517 AP_DECLARE(apr_status_t) ap_remove_input_filter_byhandle(ap_filter_t *next,
520 * Remove an output filter from either the request or connection stack
521 * it is associated with.
522 * @param next The filter stack to search
523 * @param handle The filter handle (name) to remove
524 * @return APR_SUCCESS on removal or error
526 AP_DECLARE(apr_status_t) ap_remove_output_filter_byhandle(ap_filter_t *next,
529 /* The next two filters are for abstraction purposes only. They could be
530 * done away with, but that would require that we break modules if we ever
531 * want to change our filter registration method. The basic idea, is that
532 * all filters have a place to store data, the ctx pointer. These functions
533 * fill out that pointer with a bucket brigade, and retrieve that data on
534 * the next call. The nice thing about these functions, is that they
535 * automatically concatenate the bucket brigades together for you. This means
536 * that if you have already stored a brigade in the filters ctx pointer, then
537 * when you add more it will be tacked onto the end of that brigade. When
538 * you retrieve data, if you pass in a bucket brigade to the get function,
539 * it will append the current brigade onto the one that you are retrieving.
543 * Prepare a bucket brigade to be setaside. If a different brigade was
544 * set-aside earlier, then the two brigades are concatenated together.
546 * If *save_to is NULL, the brigade will be created, and a cleanup registered
547 * to clear the brigade address when the pool is destroyed.
548 * @param f The current filter
549 * @param save_to The brigade that was previously set-aside. Regardless, the
550 * new bucket brigade is returned in this location.
551 * @param b The bucket brigade to save aside. This brigade is always empty
553 * @param p Ensure that all data in the brigade lives as long as this pool
555 AP_DECLARE(apr_status_t) ap_save_brigade(ap_filter_t *f,
556 apr_bucket_brigade **save_to,
557 apr_bucket_brigade **b, apr_pool_t *p);
560 * Prepare the filter to allow brigades to be set aside. This can be used
561 * within an input filter to allocate space to set aside data in the input
562 * filters, or can be used within an output filter by being called via
563 * ap_filter_setaside_brigade().
564 * @param f The current filter
565 * @param pool The pool that was used to create the brigade. In a request
566 * filter this will be the request pool, in a connection filter this will
567 * be the connection pool.
568 * @returns OK if a brigade was created, DECLINED otherwise.
570 AP_DECLARE(int) ap_filter_prepare_brigade(ap_filter_t *f, apr_pool_t **p);
573 * Prepare a bucket brigade to be setaside, creating a dedicated pool if
574 * necessary within the filter to handle the lifetime of the setaside brigade.
575 * @param f The current filter
576 * @param bb The bucket brigade to set aside. This brigade is always empty
579 AP_DECLARE(apr_status_t) ap_filter_setaside_brigade(ap_filter_t *f,
580 apr_bucket_brigade *bb);
583 * Reinstate a brigade setaside earlier, and calculate the amount of data we
584 * should write based on the presence of flush buckets, size limits on in
585 * memory buckets, and the number of outstanding requests in the pipeline.
586 * This is a safety mechanism to protect against a module that might try
587 * generate data too quickly for downstream to handle without yielding as
590 * If the brigade passed in is empty, we reinstate the brigade and return
591 * immediately on the assumption that any buckets needing to be flushed were
592 * flushed before being passed to ap_filter_setaside_brigade().
594 * @param f The current filter
595 * @param bb The bucket brigade to restore to.
596 * @param flush_upto Work out the bucket we need to flush up to, based on the
597 * presence of a flush bucket, size limits on in-memory
598 * buckets, size limits on the number of requests outstanding
600 * @return APR_SUCCESS.
602 AP_DECLARE(apr_status_t) ap_filter_reinstate_brigade(ap_filter_t *f,
603 apr_bucket_brigade *bb,
604 apr_bucket **flush_upto);
607 * This function calculates whether there are any as yet unsent
608 * buffered brigades in downstream filters, and returns non zero
611 * A filter should use this to determine whether the passing of data
612 * downstream might block, and so defer the passing of brigades
613 * downstream with ap_filter_setaside_brigade().
615 * This function can be called safely from a handler.
617 AP_DECLARE(int) ap_filter_should_yield(ap_filter_t *f);
620 * This function determines whether there is unwritten data in the output
621 * filters, and if so, attempts to make a single write to each filter
622 * with unwritten data.
624 * @param c The connection.
625 * @return If no unwritten data remains, this function returns DECLINED.
626 * If some unwritten data remains, this function returns OK. If any
627 * attempt to write data failed, this functions returns a positive integer.
629 AP_DECLARE(int) ap_filter_output_pending(conn_rec *c);
632 * This function determines whether there is pending data in the input
633 * filters. Pending data is data that has been read from the underlying
634 * socket but not yet returned to the application.
636 * @param c The connection.
637 * @return If no pending data remains, this function returns DECLINED.
638 * If some pending data remains, this function returns OK.
640 AP_DECLARE(int) ap_filter_input_pending(conn_rec *c);
643 * Flush function for apr_brigade_* calls. This calls ap_pass_brigade
644 * to flush the brigade if the brigade buffer overflows.
645 * @param bb The brigade to flush
646 * @param ctx The filter to pass the brigade to
647 * @note this function has nothing to do with FLUSH buckets. It is simply
648 * a way to flush content out of a brigade and down a filter stack.
650 AP_DECLARE_NONSTD(apr_status_t) ap_filter_flush(apr_bucket_brigade *bb,
654 * Flush the current brigade down the filter stack.
655 * @param f The filter we are passing to
656 * @param bb The brigade to flush
658 AP_DECLARE(apr_status_t) ap_fflush(ap_filter_t *f, apr_bucket_brigade *bb);
661 * Write a buffer for the current filter, buffering if possible.
662 * @param f the filter we are writing to
663 * @param bb The brigade to buffer into
664 * @param data The data to write
665 * @param nbyte The number of bytes in the data
667 #define ap_fwrite(f, bb, data, nbyte) \
668 apr_brigade_write(bb, ap_filter_flush, f, data, nbyte)
671 * Write a buffer for the current filter, buffering if possible.
672 * @param f the filter we are writing to
673 * @param bb The brigade to buffer into
674 * @param str The string to write
676 #define ap_fputs(f, bb, str) \
677 apr_brigade_write(bb, ap_filter_flush, f, str, strlen(str))
680 * Write a character for the current filter, buffering if possible.
681 * @param f the filter we are writing to
682 * @param bb The brigade to buffer into
683 * @param c The character to write
685 #define ap_fputc(f, bb, c) \
686 apr_brigade_putc(bb, ap_filter_flush, f, c)
689 * Write an unspecified number of strings to the current filter
690 * @param f the filter we are writing to
691 * @param bb The brigade to buffer into
692 * @param ... The strings to write
694 AP_DECLARE_NONSTD(apr_status_t) ap_fputstrs(ap_filter_t *f,
695 apr_bucket_brigade *bb,
700 * Output data to the filter in printf format
701 * @param f the filter we are writing to
702 * @param bb The brigade to buffer into
703 * @param fmt The format string
704 * @param ... The arguments to use to fill out the format string
706 AP_DECLARE_NONSTD(apr_status_t) ap_fprintf(ap_filter_t *f,
707 apr_bucket_brigade *bb,
710 __attribute__((format(printf,3,4)));
713 * set protocol requirements for an output content filter
714 * (only works with AP_FTYPE_RESOURCE and AP_FTYPE_CONTENT_SET)
715 * @param f the filter in question
716 * @param proto_flags Logical OR of AP_FILTER_PROTO_* bits
718 AP_DECLARE(void) ap_filter_protocol(ap_filter_t* f, unsigned int proto_flags);
720 /** Filter changes contents (so invalidating checksums/etc) */
721 #define AP_FILTER_PROTO_CHANGE 0x1
723 /** Filter changes length of contents (so invalidating content-length/etc) */
724 #define AP_FILTER_PROTO_CHANGE_LENGTH 0x2
726 /** Filter requires complete input and can't work on byteranges */
727 #define AP_FILTER_PROTO_NO_BYTERANGE 0x4
729 /** Filter should not run in a proxy */
730 #define AP_FILTER_PROTO_NO_PROXY 0x8
732 /** Filter makes output non-cacheable */
733 #define AP_FILTER_PROTO_NO_CACHE 0x10
735 /** Filter is incompatible with "Cache-Control: no-transform" */
736 #define AP_FILTER_PROTO_TRANSFORM 0x20
746 #endif /* !AP_FILTER_H */