Fixing schema validation" #37

subnetmarco · 2015-02-25T12:09:55Z

No description provided.

subnetmarco · 2015-02-25T13:05:38Z

Also closes #36

Fixing schema validation"

…function responses (#37) Implementing functionality to support 'isBase64Encoded' flag in Lambda function response, plugin will now base64 decode response body from Lambda before forwarding to caller

### Summary #### bug fixes - ***:** popup errors from lower functions [a19e9c8](fffonion/lua-resty-acme@a19e9c8) - **autossl:** pass storage config to acme client ([#43](fffonion/lua-resty-acme#43)) [ef1e541](fffonion/lua-resty-acme@ef1e541) #### features - **autossl:** add challenge_start_delay [df4ba0b](fffonion/lua-resty-acme@df4ba0b) - **autossl:** check if domain is whitelisted before cert renewal ([#35](fffonion/lua-resty-acme#35)) [942c007](fffonion/lua-resty-acme@942c007) - **client:** add challenge_start_callback [1c9b2d5](fffonion/lua-resty-acme@1c9b2d5) - **client:** allow to read "alternate" link and select preferred chain ([#42](fffonion/lua-resty-acme#42)) [ff17a74](fffonion/lua-resty-acme@ff17a74) - **storage/vault:** add support for kubernetes auth ([#37](fffonion/lua-resty-acme#37)) [93c2121](fffonion/lua-resty-acme@93c2121)

This eases debugging since the old error messages might have led people to think the server generated the error. fixes #37

OpenAPI spec in DevPortal or updating a big config entry for plugins, they can not work as expected. With the new parameter, the user can decide the payload size to meet their needs. In this PR, a new parameter, `worker_events_max_payload` is added, which allows to specify the payload size the `worker_events` lib can accept. The default size is 64k, and the max allowed to set is 16M Bytes. The corresponding PR for `worker_events` lib is [#37](Kong/lua-resty-events#37) FTI-4963

#11214) * With a hard-coded payload size, for some use cases like uploading a big OpenAPI spec in DevPortal or updating a big config entry for plugins, they can not work as expected. With the new parameter, the user can decide the payload size to meet their needs. In this PR, a new parameter, `worker_events_max_payload` is added, which allows to specify the payload size the `worker_events` lib can accept. The default size is 64k, and the max allowed to set is 16M Bytes. The corresponding PR for `worker_events` lib is [#37](Kong/lua-resty-events#37) FTI-4963 * add changelog entry * Update kong.conf.default Co-authored-by: Datong Sun <datong.sun@konghq.com> * add test case and bump lua-resty-events * correct the default value, and add an entry for bumping the version of lua-resty-events * 1. append PR number to the changelog entry of lua-resty-events 2. correct the spec test 3. style * Update CHANGELOG.md --------- Co-authored-by: Datong Sun <datong.sun@konghq.com> Co-authored-by: Chrono <chrono_cpp@me.com>

#11214) * With a hard-coded payload size, for some use cases like uploading a big OpenAPI spec in DevPortal or updating a big config entry for plugins, they can not work as expected. With the new parameter, the user can decide the payload size to meet their needs. In this PR, a new parameter, `worker_events_max_payload` is added, which allows to specify the payload size the `worker_events` lib can accept. The default size is 64k, and the max allowed to set is 16M Bytes. The corresponding PR for `worker_events` lib is [#37](Kong/lua-resty-events#37) FTI-4963 * add changelog entry * Update kong.conf.default Co-authored-by: Datong Sun <datong.sun@konghq.com> * add test case and bump lua-resty-events * correct the default value, and add an entry for bumping the version of lua-resty-events * 1. append PR number to the changelog entry of lua-resty-events 2. correct the spec test 3. style * Update CHANGELOG.md --------- Co-authored-by: Datong Sun <datong.sun@konghq.com> Co-authored-by: Chrono <chrono_cpp@me.com> (cherry picked from commit ff59edb)

#11214) * With a hard-coded payload size, for some use cases like uploading a big OpenAPI spec in DevPortal or updating a big config entry for plugins, they can not work as expected. With the new parameter, the user can decide the payload size to meet their needs. In this PR, a new parameter, `worker_events_max_payload` is added, which allows to specify the payload size the `worker_events` lib can accept. The default size is 64k, and the max allowed to set is 16M Bytes. The corresponding PR for `worker_events` lib is [#37](Kong/lua-resty-events#37) FTI-4963 * add changelog entry * Update kong.conf.default Co-authored-by: Datong Sun <datong.sun@konghq.com> * add test case and bump lua-resty-events * correct the default value, and add an entry for bumping the version of lua-resty-events * 1. append PR number to the changelog entry of lua-resty-events 2. correct the spec test 3. style * Update CHANGELOG.md --------- Co-authored-by: Datong Sun <datong.sun@konghq.com> Co-authored-by: Chrono <chrono_cpp@me.com>

#11214) * With a hard-coded payload size, for some use cases like uploading a big OpenAPI spec in DevPortal or updating a big config entry for plugins, they can not work as expected. With the new parameter, the user can decide the payload size to meet their needs. In this PR, a new parameter, `worker_events_max_payload` is added, which allows to specify the payload size the `worker_events` lib can accept. The default size is 64k, and the max allowed to set is 16M Bytes. The corresponding PR for `worker_events` lib is [#37](Kong/lua-resty-events#37) FTI-4963 * add changelog entry * Update kong.conf.default Co-authored-by: Datong Sun <datong.sun@konghq.com> * add test case and bump lua-resty-events * correct the default value, and add an entry for bumping the version of lua-resty-events * 1. append PR number to the changelog entry of lua-resty-events 2. correct the spec test 3. style * Update CHANGELOG.md --------- Co-authored-by: Datong Sun <datong.sun@konghq.com> Co-authored-by: Chrono <chrono_cpp@me.com> (cherry picked from commit ff59edb)

subnetmarco added 5 commits February 25, 2015 04:09

Fixing schema validation"

9bd5c5c

fixing import and removing debug info

df675ff

fixing constant value

9f2218a

bugfix

b58507d

fixing logic in authentication schema

db43a82

subnetmarco added a commit that referenced this pull request Feb 25, 2015

Merge pull request #37 from Mashape/fix/schema-validation

2236374

Fixing schema validation"

subnetmarco merged commit 2236374 into master Feb 25, 2015

subnetmarco deleted the fix/schema-validation branch February 25, 2015 13:05

subnetmarco mentioned this pull request Feb 25, 2015

Base DAO exception (concatenate field) #35

Closed

ctranxuan pushed a commit to streamdataio/kong that referenced this pull request Aug 25, 2015

Merge pull request Kong#37 from Mashape/fix/schema-validation

9495882

Fixing schema validation"

gszr pushed a commit that referenced this pull request Jul 7, 2021

doc(readme) add declarative configuration sample (#37)

ce558c7

javierguerragiraldez pushed a commit that referenced this pull request Sep 3, 2021

fix(client) clearly mark client errors as such (#40)

2f6b954

This eases debugging since the old error messages might have led people to think the server generated the error. fixes #37

hutchic added a commit that referenced this pull request Jun 10, 2022

feat(src) src release to bintray (#37)

304f55c

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Fixing schema validation" #37

Fixing schema validation" #37

subnetmarco commented Feb 25, 2015

subnetmarco commented Feb 25, 2015

Fixing schema validation" #37

Fixing schema validation" #37

Conversation

subnetmarco commented Feb 25, 2015

subnetmarco commented Feb 25, 2015