Kotlin language specification
Version 1.9-rfc+0.10 码力 | 310 页 | 1.39 MB | 1 年前3- Kotlin language specification
Version 1.9-rfc+0.10 码力 | 38 页 | 358.59 KB | 1 年前3
Falcon v3.0.1 DocumentationNote 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 --AaB03x0 码力 | 1058 页 | 741.59 KB | 1 年前3- Falcon v3.0.0 DocumentationNote 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 --AaB03x0 码力 | 1055 页 | 739.30 KB | 1 年前3
- Falcon v3.1.1 DocumentationNote 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 --AaB03x0 码力 | 540 页 | 476.60 KB | 1 年前3
- Falcon v3.1.1-rc1 DocumentationNote 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 --AaB03x0 码力 | 540 页 | 476.61 KB | 1 年前3
- Falcon v3.1.0 DocumentationNote 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 --AaB03x0 码力 | 537 页 | 474.34 KB | 1 年前3
- Falcon v3.1.1-b3 DocumentationNote 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 --AaB03x0 码力 | 540 页 | 476.61 KB | 1 年前3
- Falcon v3.1.1-a DocumentationNote 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 --AaB03x0 码力 | 540 页 | 476.60 KB | 1 年前3
- Falcon v3.1.1-b1 DocumentationNote 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 --AaB03x0 码力 | 540 页 | 476.61 KB | 1 年前3
共 1000 条
- 1
- 2
- 3
- 4
- 5
- 6
- 100