mirrors
/
kore
mirror of https://git.kore.io/kore.git
1
0
Fork 1
Code Issues Projects Releases Wiki Activity
kore/examples/integers/conf/integers.conf

28 lines
377 B
Plaintext
Raw Normal View History

Add integers example
2014-08-03 20:29:24 +02:00
# Placeholder configuration
Allow multiple binds on new server directive.
2019-09-27 20:00:35 +02:00
server tls {
Allow listening of tls/notls ports at the same time. Before kore needed to be built with NOTLS=1 to be able to do non TLS connections. This has been like this for years. It is time to allow non TLS listeners without having to rebuild Kore. This commit changes your configuration format and will break existing applications their config. Configurations now get listener {} contexts: listen default { bind 127.0.0.1 8888 } The above will create a listener on 127.0.0.1, port 8888 that will serve TLS (still the default). If you want to turn off TLS on that listener, specify "tls no" in that context. Domains now need to be attached to a listener: Eg: domain * { attach default } For the Python API this kills kore.bind(), and kore.bind_unix(). They are replaced with: kore.listen("name", ip=None, port=None, path=None, tls=True).
2019-09-27 12:22:35 +02:00
bind 127.0.0.1 8888
}
Add integers example
2014-08-03 20:29:24 +02:00
load ./integers.so
Add HTTP_REQUEST_RETAIN_EXTRA flag to http_request Signals Kore to not free any pointer set in req->hdlr_extra. Useful in certain scenarios where you have data per request bound to something in memory but do not want to lose it when the request is freed by Kore. Set this flag before your handler returns.
2015-03-27 23:23:21 +01:00
workers 2
worker_max_connections 5000
Default to only TLSv1.2 from now on. Add configuration setting tls_version to specify if you either want TLSv1.2 or TLSv1.0 or both. The configuration options ssl_cipher and ssl_dhparam have changed name to tls_cipher and tls_dhparam. There is no fallback so you might have to update your configs.
2015-05-06 10:59:43 +02:00
tls_dhparam dh2048.pem
Add missing ssl_dhparam to all example configs.
2015-02-06 09:02:29 +01:00
Add kore_strtodouble(). Use it for http_argument_get_float() and http_argument_get_double().
2018-05-04 15:55:35 +02:00
validator v_id regex ^-?[0-9]*.?[0-9]+$
Add integers example
2014-08-03 20:29:24 +02:00
change all domain directives to * in examples.
2017-09-19 15:16:02 +02:00
domain * {
Allow listening of tls/notls ports at the same time. Before kore needed to be built with NOTLS=1 to be able to do non TLS connections. This has been like this for years. It is time to allow non TLS listeners without having to rebuild Kore. This commit changes your configuration format and will break existing applications their config. Configurations now get listener {} contexts: listen default { bind 127.0.0.1 8888 } The above will create a listener on 127.0.0.1, port 8888 that will serve TLS (still the default). If you want to turn off TLS on that listener, specify "tls no" in that context. Domains now need to be attached to a listener: Eg: domain * { attach default } For the Python API this kills kore.bind(), and kore.bind_unix(). They are replaced with: kore.listen("name", ip=None, port=None, path=None, tls=True).
2019-09-27 12:22:35 +02:00
attach tls
Adjust examples after recent changes. - New kodev tool generates config with server.pem/key.pem. - Use proper formats for kore_log(). - Update to new websocket api.
2017-02-26 02:02:39 +01:00
certfile cert/server.pem
certkey cert/key.pem
Replace static/dynamic with a single option: route Kore will automatically detect if a route is a dynamic or static one so there is no need for the configuration options to differ anymore.
2019-11-15 08:11:02 +01:00
route / page
Add integers example
2014-08-03 20:29:24 +02:00
Allow param blocks to be marked as "querystring" Before params get would mean querystring and anything else would just count toward a www-encoded body. Now you can prefix the params block with "qs" indicating that those configured parameters are allowed to occur in the query string regardless of the method used. This means you can do something like: params qs:post /uri { ... } to specify what the allowed parameters are in the querystring for a POST request towards /uri. inspired by and properly fixes #205.
2018-01-16 18:47:50 +01:00
# allowed parameters in the query string for GETs
params qs:get / {
Add integers example
2014-08-03 20:29:24 +02:00
validate id v_id
}
}