michaelh/zephyr
1
0
Fork 0
Code Releases Activity
zephyr/subsys/net/lib/http/Kconfig

104 lines
2.5 KiB
Text
Raw Normal View History

iot: Add HTTP support for Zephyr This commit adds HTTP message handling support for Zephyr. So, no network routines are involved at this level. To add HTTP message handling support for Zephyr, we explored the following options: 1. Importing an external project and perhaps adapting it to fit our requirements. The criteria to pick one codebase among all the available projects are: licensing, correctness and performance. 2. Writing our own implementation from scratch. We decided to import an external project instead of implementing our own parser, mainly due to code maturity and correctness. It could take more time to obtain a production-ready parser from scratch than adapting a state-of-art library. The following is a list of some projects offering similar functionality. lighttpd (many files) * License: revised BSD license * Supported: active * Comments: this parser can't be integrated to Zephyr due to dependencies that currently are not satisficed by our SDK. nginx (src/http/ngx_http_parse.c) * License: 2-clause BSD-like * Supported: very active * Comments: this parser can't be integrated to Zephyr due to dependencies that currently are not satisficed by our SDK. wget (src/http-parse.c) * License: GPL 3.0 * Supported: very active * Comments: this code can't be included in Zephyr due to licensing issues curl (lib/http.c) * License: MIT/X derivate, see: https://curl.haxx.se/docs/copyright.html * Supported: very active * Comment: it must be forked and adapted to run in Zephyr. It is not optimized for low-power devices. nodejs http-parser (http_parser.c) * License: nginx license (2-clause BSD-like) and MIT license * Supported: very active * Comments: optimized with performance in mind. From https://github.com/nodejs/http-parser: "It does not make any syscalls nor allocations, it does not buffer data, it can be interrupted at anytime. It only requires about 40 bytes of data per message stream." So, nodejs/http-parser looks a very good choice for Zephyr. In this commit, we integrate nodejs' parser to Zephyr. Origin: https://github.com/nodejs/http-parser/releases/tag/v2.7.1 https://github.com/nodejs/http-parser/archive/v2.7.1.tar.gz NOTE: This patch reformats the http_parser files to reduce checkpatch warnings. Changes made in this refactoring are available at: Repo: https://gitlab.com/santes/http_parser/commits/refactoring1 Commit: 9ccfaa23f1c8438855211fa902ec8e7236b702b1 Jira: ZEP-346 Jira: ZEP-776 Change-Id: I29b1d47f323a5841cd4d0a2afbc2cc83a0f576f0 Signed-off-by: Flavio Santes <flavio.santes@intel.com>
2016-08-31 21:46:36 -05:00
# Copyright (c) 2016 Intel Corporation
#
license: Replace Apache boilerplate with SPDX tag Replace the existing Apache 2.0 boilerplate header with an SPDX tag throughout the zephyr code tree. This patch was generated via a script run over the master branch. Also updated doc/porting/application.rst that had a dependency on line numbers in a literal include. Manually updated subsys/logging/sys_log.c that had a malformed header in the original file. Also cleanup several cases that already had a SPDX tag and we either got a duplicate or missed updating. Jira: ZEP-1457 Change-Id: I6131a1d4ee0e58f5b938300c2d2fc77d2e69572c Signed-off-by: David B. Kinder <david.b.kinder@intel.com> Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
2017-01-18 17:01:01 -08:00
# SPDX-License-Identifier: Apache-2.0
iot: Add HTTP support for Zephyr This commit adds HTTP message handling support for Zephyr. So, no network routines are involved at this level. To add HTTP message handling support for Zephyr, we explored the following options: 1. Importing an external project and perhaps adapting it to fit our requirements. The criteria to pick one codebase among all the available projects are: licensing, correctness and performance. 2. Writing our own implementation from scratch. We decided to import an external project instead of implementing our own parser, mainly due to code maturity and correctness. It could take more time to obtain a production-ready parser from scratch than adapting a state-of-art library. The following is a list of some projects offering similar functionality. lighttpd (many files) * License: revised BSD license * Supported: active * Comments: this parser can't be integrated to Zephyr due to dependencies that currently are not satisficed by our SDK. nginx (src/http/ngx_http_parse.c) * License: 2-clause BSD-like * Supported: very active * Comments: this parser can't be integrated to Zephyr due to dependencies that currently are not satisficed by our SDK. wget (src/http-parse.c) * License: GPL 3.0 * Supported: very active * Comments: this code can't be included in Zephyr due to licensing issues curl (lib/http.c) * License: MIT/X derivate, see: https://curl.haxx.se/docs/copyright.html * Supported: very active * Comment: it must be forked and adapted to run in Zephyr. It is not optimized for low-power devices. nodejs http-parser (http_parser.c) * License: nginx license (2-clause BSD-like) and MIT license * Supported: very active * Comments: optimized with performance in mind. From https://github.com/nodejs/http-parser: "It does not make any syscalls nor allocations, it does not buffer data, it can be interrupted at anytime. It only requires about 40 bytes of data per message stream." So, nodejs/http-parser looks a very good choice for Zephyr. In this commit, we integrate nodejs' parser to Zephyr. Origin: https://github.com/nodejs/http-parser/releases/tag/v2.7.1 https://github.com/nodejs/http-parser/archive/v2.7.1.tar.gz NOTE: This patch reformats the http_parser files to reduce checkpatch warnings. Changes made in this refactoring are available at: Repo: https://gitlab.com/santes/http_parser/commits/refactoring1 Commit: 9ccfaa23f1c8438855211fa902ec8e7236b702b1 Jira: ZEP-346 Jira: ZEP-776 Change-Id: I29b1d47f323a5841cd4d0a2afbc2cc83a0f576f0 Signed-off-by: Flavio Santes <flavio.santes@intel.com>
2016-08-31 21:46:36 -05:00
#
net/http: Add the HTTP/1.1 API This patch adds the HTTP/1.1 API for Zephyr. This API consists of client and server context structures enabled via Kconfig variables. HTTP parser support is enabled via the CONFIG_HTTP_PARSER configuration variable. Currently, this API only includes support for writing HTTP requests (client mode) and HTTP responses (server mode). TLS support is not considered in this iteration. Supported HTTP methods: GET, HEAD, OPTIONS and POST. Supported HTTP responses: 400, 403 404. The http_response routine may be used to write any HTTP status code, for example 200 OK. Jira: ZEP-1701 Change-Id: Ic9ccd4d4578d6d0f3a439976ea332b031644ca7d Signed-off-by: Flavio Santes <flavio.santes@intel.com>
2017-02-21 15:02:00 -06:00
config HTTP
http: client: Create a HTTP library Instead of separate sample application that does everything related to HTTP client connectivity, create a HTTP client library that hides nasty details that are related to sending HTTP methods. After this the sample HTTP client application is very simple and only shows how to use the client HTTP API. Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
2017-04-25 17:58:18 +03:00
bool "HTTP support"
net/http: Add the HTTP/1.1 API This patch adds the HTTP/1.1 API for Zephyr. This API consists of client and server context structures enabled via Kconfig variables. HTTP parser support is enabled via the CONFIG_HTTP_PARSER configuration variable. Currently, this API only includes support for writing HTTP requests (client mode) and HTTP responses (server mode). TLS support is not considered in this iteration. Supported HTTP methods: GET, HEAD, OPTIONS and POST. Supported HTTP responses: 400, 403 404. The http_response routine may be used to write any HTTP status code, for example 200 OK. Jira: ZEP-1701 Change-Id: Ic9ccd4d4578d6d0f3a439976ea332b031644ca7d Signed-off-by: Flavio Santes <flavio.santes@intel.com>
2017-02-21 15:02:00 -06:00
help
kconfig: fix help syntax and add spaces Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2017-12-13 10:08:21 -05:00
This option enables the HTTP library
net/http: Add the HTTP/1.1 API This patch adds the HTTP/1.1 API for Zephyr. This API consists of client and server context structures enabled via Kconfig variables. HTTP parser support is enabled via the CONFIG_HTTP_PARSER configuration variable. Currently, this API only includes support for writing HTTP requests (client mode) and HTTP responses (server mode). TLS support is not considered in this iteration. Supported HTTP methods: GET, HEAD, OPTIONS and POST. Supported HTTP responses: 400, 403 404. The http_response routine may be used to write any HTTP status code, for example 200 OK. Jira: ZEP-1701 Change-Id: Ic9ccd4d4578d6d0f3a439976ea332b031644ca7d Signed-off-by: Flavio Santes <flavio.santes@intel.com>
2017-02-21 15:02:00 -06:00
net: http: Create HTTP library that uses net-app Create http library that uses net-app instead of net_context directly. The old HTTP API is deprecated. Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
2017-10-02 16:44:48 +03:00
if HTTP
net/http: Add the HTTP/1.1 API This patch adds the HTTP/1.1 API for Zephyr. This API consists of client and server context structures enabled via Kconfig variables. HTTP parser support is enabled via the CONFIG_HTTP_PARSER configuration variable. Currently, this API only includes support for writing HTTP requests (client mode) and HTTP responses (server mode). TLS support is not considered in this iteration. Supported HTTP methods: GET, HEAD, OPTIONS and POST. Supported HTTP responses: 400, 403 404. The http_response routine may be used to write any HTTP status code, for example 200 OK. Jira: ZEP-1701 Change-Id: Ic9ccd4d4578d6d0f3a439976ea332b031644ca7d Signed-off-by: Flavio Santes <flavio.santes@intel.com>
2017-02-21 15:02:00 -06:00
config HTTP_SERVER
http: client: Create a HTTP library Instead of separate sample application that does everything related to HTTP client connectivity, create a HTTP client library that hides nasty details that are related to sending HTTP methods. After this the sample HTTP client application is very simple and only shows how to use the client HTTP API. Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
2017-04-25 17:58:18 +03:00
bool "HTTP server support"
net: http: Add HTTP server library support This commit creates a HTTP server library. So instead of creating a complex HTTP server application for serving HTTP requests, the developer can use the HTTP server API to create HTTP server insteances. This commit also adds support for creating HTTPS servers. Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
2017-05-08 14:27:29 +03:00
select HTTP_PARSER
net: http: Create HTTP library that uses net-app Create http library that uses net-app instead of net_context directly. The old HTTP API is deprecated. Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
2017-10-02 16:44:48 +03:00
select HTTP_PARSER_URL
select NET_APP_SERVER
net/http: Add the HTTP/1.1 API This patch adds the HTTP/1.1 API for Zephyr. This API consists of client and server context structures enabled via Kconfig variables. HTTP parser support is enabled via the CONFIG_HTTP_PARSER configuration variable. Currently, this API only includes support for writing HTTP requests (client mode) and HTTP responses (server mode). TLS support is not considered in this iteration. Supported HTTP methods: GET, HEAD, OPTIONS and POST. Supported HTTP responses: 400, 403 404. The http_response routine may be used to write any HTTP status code, for example 200 OK. Jira: ZEP-1701 Change-Id: Ic9ccd4d4578d6d0f3a439976ea332b031644ca7d Signed-off-by: Flavio Santes <flavio.santes@intel.com>
2017-02-21 15:02:00 -06:00
help
kconfig: fix help syntax and add spaces Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2017-12-13 10:08:21 -05:00
Enables HTTP server routines.
net: http: Add HTTP server library support This commit creates a HTTP server library. So instead of creating a complex HTTP server application for serving HTTP requests, the developer can use the HTTP server API to create HTTP server insteances. This commit also adds support for creating HTTPS servers. Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
2017-05-08 14:27:29 +03:00
net: http: Create HTTP library that uses net-app Create http library that uses net-app instead of net_context directly. The old HTTP API is deprecated. Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
2017-10-02 16:44:48 +03:00
config HTTP_CLIENT
bool "HTTP client support"
select HTTP_PARSER
select HTTP_PARSER_URL
select NET_APP_CLIENT
net: http: Add HTTP server library support This commit creates a HTTP server library. So instead of creating a complex HTTP server application for serving HTTP requests, the developer can use the HTTP server API to create HTTP server insteances. This commit also adds support for creating HTTPS servers. Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
2017-05-08 14:27:29 +03:00
help
kconfig: fix help syntax and add spaces Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2017-12-13 10:08:21 -05:00
Enables HTTP client routines.
net: http: Add HTTP server library support This commit creates a HTTP server library. So instead of creating a complex HTTP server application for serving HTTP requests, the developer can use the HTTP server API to create HTTP server insteances. This commit also adds support for creating HTTPS servers. Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
2017-05-08 14:27:29 +03:00
net: http: Create HTTP library that uses net-app Create http library that uses net-app instead of net_context directly. The old HTTP API is deprecated. Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
2017-10-02 16:44:48 +03:00
config HTTP_HEADERS
http: client: Create a HTTP library Instead of separate sample application that does everything related to HTTP client connectivity, create a HTTP client library that hides nasty details that are related to sending HTTP methods. After this the sample HTTP client application is very simple and only shows how to use the client HTTP API. Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
2017-04-25 17:58:18 +03:00
int "HTTP header field max number of items"
net/http: Add the HTTP/1.1 API This patch adds the HTTP/1.1 API for Zephyr. This API consists of client and server context structures enabled via Kconfig variables. HTTP parser support is enabled via the CONFIG_HTTP_PARSER configuration variable. Currently, this API only includes support for writing HTTP requests (client mode) and HTTP responses (server mode). TLS support is not considered in this iteration. Supported HTTP methods: GET, HEAD, OPTIONS and POST. Supported HTTP responses: 400, 403 404. The http_response routine may be used to write any HTTP status code, for example 200 OK. Jira: ZEP-1701 Change-Id: Ic9ccd4d4578d6d0f3a439976ea332b031644ca7d Signed-off-by: Flavio Santes <flavio.santes@intel.com>
2017-02-21 15:02:00 -06:00
depends on HTTP_SERVER
default 8
net: websocket: Initial support for server websocket This commit creates a websocket library that can be used by applications. The websocket library implements currently only server role and it uses services provided by net-app API. The library supports TLS if enabled in configuration file. This also adds websocket calls to HTTP app server if websocket connection is established. Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
2017-08-20 23:15:07 +03:00
default 20 if WEBSOCKET
net/http: Add the HTTP/1.1 API This patch adds the HTTP/1.1 API for Zephyr. This API consists of client and server context structures enabled via Kconfig variables. HTTP parser support is enabled via the CONFIG_HTTP_PARSER configuration variable. Currently, this API only includes support for writing HTTP requests (client mode) and HTTP responses (server mode). TLS support is not considered in this iteration. Supported HTTP methods: GET, HEAD, OPTIONS and POST. Supported HTTP responses: 400, 403 404. The http_response routine may be used to write any HTTP status code, for example 200 OK. Jira: ZEP-1701 Change-Id: Ic9ccd4d4578d6d0f3a439976ea332b031644ca7d Signed-off-by: Flavio Santes <flavio.santes@intel.com>
2017-02-21 15:02:00 -06:00
help
kconfig: fix help syntax and add spaces Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2017-12-13 10:08:21 -05:00
Number of HTTP header field items that an HTTP server
net: websocket: Initial support for server websocket This commit creates a websocket library that can be used by applications. The websocket library implements currently only server role and it uses services provided by net-app API. The library supports TLS if enabled in configuration file. This also adds websocket calls to HTTP app server if websocket connection is established. Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
2017-08-20 23:15:07 +03:00
application will handle. If websocket is enabled, then the
default needs to be much bigger.
net/http: Add the HTTP/1.1 API This patch adds the HTTP/1.1 API for Zephyr. This API consists of client and server context structures enabled via Kconfig variables. HTTP parser support is enabled via the CONFIG_HTTP_PARSER configuration variable. Currently, this API only includes support for writing HTTP requests (client mode) and HTTP responses (server mode). TLS support is not considered in this iteration. Supported HTTP methods: GET, HEAD, OPTIONS and POST. Supported HTTP responses: 400, 403 404. The http_response routine may be used to write any HTTP status code, for example 200 OK. Jira: ZEP-1701 Change-Id: Ic9ccd4d4578d6d0f3a439976ea332b031644ca7d Signed-off-by: Flavio Santes <flavio.santes@intel.com>
2017-02-21 15:02:00 -06:00
net: http: Create HTTP library that uses net-app Create http library that uses net-app instead of net_context directly. The old HTTP API is deprecated. Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
2017-10-02 16:44:48 +03:00
config HTTPS
bool "HTTPS support"
select NET_APP_TLS
net/http: Add the HTTP/1.1 API This patch adds the HTTP/1.1 API for Zephyr. This API consists of client and server context structures enabled via Kconfig variables. HTTP parser support is enabled via the CONFIG_HTTP_PARSER configuration variable. Currently, this API only includes support for writing HTTP requests (client mode) and HTTP responses (server mode). TLS support is not considered in this iteration. Supported HTTP methods: GET, HEAD, OPTIONS and POST. Supported HTTP responses: 400, 403 404. The http_response routine may be used to write any HTTP status code, for example 200 OK. Jira: ZEP-1701 Change-Id: Ic9ccd4d4578d6d0f3a439976ea332b031644ca7d Signed-off-by: Flavio Santes <flavio.santes@intel.com>
2017-02-21 15:02:00 -06:00
help
kconfig: fix help syntax and add spaces Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2017-12-13 10:08:21 -05:00
Enables HTTPS support.
net/http: Add the HTTP/1.1 API This patch adds the HTTP/1.1 API for Zephyr. This API consists of client and server context structures enabled via Kconfig variables. HTTP parser support is enabled via the CONFIG_HTTP_PARSER configuration variable. Currently, this API only includes support for writing HTTP requests (client mode) and HTTP responses (server mode). TLS support is not considered in this iteration. Supported HTTP methods: GET, HEAD, OPTIONS and POST. Supported HTTP responses: 400, 403 404. The http_response routine may be used to write any HTTP status code, for example 200 OK. Jira: ZEP-1701 Change-Id: Ic9ccd4d4578d6d0f3a439976ea332b031644ca7d Signed-off-by: Flavio Santes <flavio.santes@intel.com>
2017-02-21 15:02:00 -06:00
net: http: Create HTTP library that uses net-app Create http library that uses net-app instead of net_context directly. The old HTTP API is deprecated. Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
2017-10-02 16:44:48 +03:00
config HTTP_SERVER_CONNECTIONS
int "Max number of concurrent HTTP server connections"
default NET_APP_SERVER_NUM_CONN
depends on HTTP_SERVER
net: http: allow HTTP_NETWORK_TIMEOUT to be configured Currently, the HTTP_NETWORK_TIMEOUT setting is hard-coded as 20 seconds. Not every application may want to wait that long, so let's change this to a CONFIG option: CONFIG_HTTP_CLIENT_NETWORK_TIMEOUT NOTE: This also removes HTTP_NETWORK_TIMEOUT from the public http.h include file. It was not being used externally to HTTP client sources. Signed-off-by: Michael Scott <michael.scott@linaro.org>
2017-08-15 16:01:03 -07:00
help
kconfig: fix help syntax and add spaces Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2017-12-13 10:08:21 -05:00
This value determines how many simultaneous HTTP connections the
HTTP server can serve. Note that only 1 HTTPS connection can be
served at a time, so set CONFIG_NET_APP_SERVER_NUM_CONN and
CONFIG_NET_TCP_BACKLOG_SIZE to 1 in that case.
net: http: allow HTTP_NETWORK_TIMEOUT to be configured Currently, the HTTP_NETWORK_TIMEOUT setting is hard-coded as 20 seconds. Not every application may want to wait that long, so let's change this to a CONFIG option: CONFIG_HTTP_CLIENT_NETWORK_TIMEOUT NOTE: This also removes HTTP_NETWORK_TIMEOUT from the public http.h include file. It was not being used externally to HTTP client sources. Signed-off-by: Michael Scott <michael.scott@linaro.org>
2017-08-15 16:01:03 -07:00
net: http: Create HTTP library that uses net-app Create http library that uses net-app instead of net_context directly. The old HTTP API is deprecated. Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
2017-10-02 16:44:48 +03:00
config HTTP_SERVER_NUM_URLS
int "Max number of URLs that the HTTP server will handle"
default 8
depends on HTTP_SERVER
help
kconfig: fix help syntax and add spaces Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2017-12-13 10:08:21 -05:00
This value determines how many URLs this HTTP server can handle.
net: http: Create HTTP library that uses net-app Create http library that uses net-app instead of net_context directly. The old HTTP API is deprecated. Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
2017-10-02 16:44:48 +03:00
config HTTP_CLIENT_NETWORK_TIMEOUT
int "Default network activity timeout in seconds"
default 20
depends on HTTP_CLIENT
help
kconfig: fix help syntax and add spaces Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2017-12-13 10:08:21 -05:00
Default network activity timeout in seconds. This setting is used
for TCP connection timeout.
net: http: Create HTTP library that uses net-app Create http library that uses net-app instead of net_context directly. The old HTTP API is deprecated. Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
2017-10-02 16:44:48 +03:00
http: client: Create a HTTP library Instead of separate sample application that does everything related to HTTP client connectivity, create a HTTP client library that hides nasty details that are related to sending HTTP methods. After this the sample HTTP client application is very simple and only shows how to use the client HTTP API. Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
2017-04-25 17:58:18 +03:00
config NET_DEBUG_HTTP
bool "Debug HTTP"
depends on HTTP && NET_LOG
help
kconfig: fix help syntax and add spaces Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2017-12-13 10:08:21 -05:00
Enables HTTP output debug messages
net: http: Collect HTTP server connection information If CONFIG_NET_DEBUG_HTTP_CONN is enabled, then start to collect currently active HTTP connections to HTTP server. This is only useful for debugging the HTTP connections. Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
2017-06-05 16:39:45 +03:00
config NET_DEBUG_HTTP_CONN
bool "Debug HTTP connections"
depends on HTTP && NET_LOG
help
kconfig: fix help syntax and add spaces Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2017-12-13 10:08:21 -05:00
Enables HTTP connection tracking.
net: http: Create HTTP library that uses net-app Create http library that uses net-app instead of net_context directly. The old HTTP API is deprecated. Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
2017-10-02 16:44:48 +03:00
endif # HTTP
config HTTP_PARSER
bool "HTTP Parser support"
select HTTP_PARSER_URL
help
kconfig: fix help syntax and add spaces Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2017-12-13 10:08:21 -05:00
This option enables the http_parser library from nodejs.
This parser requires some string-related routines commonly
provided by a libc implementation.
net: http: Create HTTP library that uses net-app Create http library that uses net-app instead of net_context directly. The old HTTP API is deprecated. Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
2017-10-02 16:44:48 +03:00
config HTTP_PARSER_URL
bool "HTTP Parser for URL support"
help
kconfig: fix help syntax and add spaces Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2017-12-13 10:08:21 -05:00
This option enables the URI parser library based on source from nodejs.
This parser requires some string-related routines commonly
provided by a libc implementation.
net: http: Create HTTP library that uses net-app Create http library that uses net-app instead of net_context directly. The old HTTP API is deprecated. Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
2017-10-02 16:44:48 +03:00
config HTTP_PARSER_STRICT
bool "HTTP strict parsing"
depends on (HTTP_PARSER || HTTP_PARSER_URL)
help
kconfig: fix help syntax and add spaces Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2017-12-13 10:08:21 -05:00
This option enables the strict parsing option
Copy permalink