Note Supported HTTP methods are those specified in RFC 7231 [https://tools.ietf.org/html/rfc7231] and RFC 5789 [https://tools.ietf.org/html/rfc5789]. This includes GET, HEAD, POST, PUT, DELETE, CONNECT [https://html.spec.whatwg.org/multipage/form-control-infrastructure.html] and RFC 7578, Section 4.3 [https://tools.ietf.org/html/rfc7578#section-4.3]. If your app needs to handle nested forms, this can be containing a nested multipart/mixed part (the example is adapted from the now-obsolete RFC 1867 [https://tools.ietf.org/html/rfc1867]): --AaB03x Content-Disposition: form-data; name="field1" Joe Blow --AaB03x

Note Supported HTTP methods are those specified in RFC 7231 [https://tools.ietf.org/html/rfc7231] and RFC 5789 [https://tools.ietf.org/html/rfc5789]. This includes GET, HEAD, POST, PUT, DELETE, CONNECT [https://html.spec.whatwg.org/multipage/form-control-infrastructure.html] and RFC 7578, Section 4.3 [https://tools.ietf.org/html/rfc7578#section-4.3]. If your app needs to handle nested forms, this can be containing a nested multipart/mixed part (the example is adapted from the now-obsolete RFC 1867 [https://tools.ietf.org/html/rfc1867]): --AaB03x Content-Disposition: form-data; name="field1" Joe Blow --AaB03x

Note Supported HTTP methods are those specified in RFC 7231 [https://tools.ietf.org/html/rfc7231] and RFC 5789 [https://tools.ietf.org/html/rfc5789]. This includes GET, HEAD, POST, PUT, DELETE, CONNECT [https://html.spec.whatwg.org/multipage/form-control-infrastructure.html] and RFC 7578, Section 4.3 [https://tools.ietf.org/html/rfc7578#section-4.3]. If your app needs to handle nested forms, this can be containing a nested multipart/mixed part (the example is adapted from the now-obsolete RFC 1867 [https://tools.ietf.org/html/rfc1867]): --AaB03x Content-Disposition: form-data; name="field1" Joe Blow --AaB03x

Note Supported HTTP methods are those specified in RFC 7231 [https://tools.ietf.org/html/rfc7231] and RFC 5789 [https://tools.ietf.org/html/rfc5789]. This includes GET, HEAD, POST, PUT, DELETE, CONNECT [https://html.spec.whatwg.org/multipage/form-control-infrastructure.html] and RFC 7578, Section 4.3 [https://tools.ietf.org/html/rfc7578#section-4.3]. If your app needs to handle nested forms, this can be containing a nested multipart/mixed part (the example is adapted from the now-obsolete RFC 1867 [https://tools.ietf.org/html/rfc1867]): --AaB03x Content-Disposition: form-data; name="field1" Joe Blow --AaB03x

Note Supported HTTP methods are those specified in RFC 7231 [https://tools.ietf.org/html/rfc7231] and RFC 5789 [https://tools.ietf.org/html/rfc5789]. This includes GET, HEAD, POST, PUT, DELETE, CONNECT [https://html.spec.whatwg.org/multipage/form-control-infrastructure.html] and RFC 7578, Section 4.3 [https://tools.ietf.org/html/rfc7578#section-4.3]. If your app needs to handle nested forms, this can be containing a nested multipart/mixed part (the example is adapted from the now-obsolete RFC 1867 [https://tools.ietf.org/html/rfc1867]): --AaB03x Content-Disposition: form-data; name="field1" Joe Blow --AaB03x

Note Supported HTTP methods are those specified in RFC 7231 [https://tools.ietf.org/html/rfc7231] and RFC 5789 [https://tools.ietf.org/html/rfc5789]. This includes GET, HEAD, POST, PUT, DELETE, CONNECT [https://html.spec.whatwg.org/multipage/form-control-infrastructure.html] and RFC 7578, Section 4.3 [https://tools.ietf.org/html/rfc7578#section-4.3]. If your app needs to handle nested forms, this can be containing a nested multipart/mixed part (the example is adapted from the now-obsolete RFC 1867 [https://tools.ietf.org/html/rfc1867]): --AaB03x Content-Disposition: form-data; name="field1" Joe Blow --AaB03x

Note Supported HTTP methods are those specified in RFC 7231 [https://tools.ietf.org/html/rfc7231] and RFC 5789 [https://tools.ietf.org/html/rfc5789]. This includes GET, HEAD, POST, PUT, DELETE, CONNECT [https://html.spec.whatwg.org/multipage/form-control-infrastructure.html] and RFC 7578, Section 4.3 [https://tools.ietf.org/html/rfc7578#section-4.3]. If your app needs to handle nested forms, this can be containing a nested multipart/mixed part (the example is adapted from the now-obsolete RFC 1867 [https://tools.ietf.org/html/rfc1867]): --AaB03x Content-Disposition: form-data; name="field1" Joe Blow --AaB03x

Note Supported HTTP methods are those specified in RFC 7231 [https://tools.ietf.org/html/rfc7231] and RFC 5789 [https://tools.ietf.org/html/rfc5789]. This includes GET, HEAD, POST, PUT, DELETE, CONNECT [https://html.spec.whatwg.org/multipage/form-control-infrastructure.html] and RFC 7578, Section 4.3 [https://tools.ietf.org/html/rfc7578#section-4.3]. If your app needs to handle nested forms, this can be containing a nested multipart/mixed part (the example is adapted from the now-obsolete RFC 1867 [https://tools.ietf.org/html/rfc1867]): --AaB03x Content-Disposition: form-data; name="field1" Joe Blow --AaB03x

tries to do as little as possible while remaining highly effective. Routes based on URI templates RFC REST-inspired mapping of URIs to resources Global, resource, and method hooks Idiomatic HTTP error percent-encoding. Therefore, Falcon, converts + to a space when decoding strings. To work around this, RFC 3986 specifies + as a reserved character, and recommends percent-encoding any such characters when Commas are a reserved character that can be escaped according to RFC 3986 - 2.2. Reserved Characters [https://tools.ietf.org/html/rfc3986#section-2.2], so one possible solution is to percent encode any

tries to do as little as possible while remaining highly effective. Routes based on URI templates RFC REST-inspired mapping of URIs to resources Global, resource, and method hooks Idiomatic HTTP error percent-encoding. Therefore, Falcon, converts + to a space when decoding strings. To work around this, RFC 3986 specifies + as a reserved character, and recommends percent-encoding any such characters when Commas are a reserved character that can be escaped according to RFC 3986 - 2.2. Reserved Characters [https://tools.ietf.org/html/rfc3986#section-2.2], so one possible solution is to percent encode any