You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 4, 2023. It is now read-only.
I discovered this error and a co-worker did the sleuthing to track down the exact problem. It turns out that curl will default to application/x-www-form-urlencoded when you don't specify a content type. And that can cause a process to crash due to an unhandled exception (at least for us) deep in the bowels of things completely outside of our code.
While driving this morning I realized that this issue is a little vague. The URL needs to be one that accepts POSTs because otherwise the debug message is circumvented, no further processing (and failing) takes place. It may also need to be running in debug mode (haven't verified yet).
I discovered this error and a co-worker did the sleuthing to track down the exact problem. It turns out that curl will default to
application/x-www-form-urlencoded
when you don't specify a content type. And that can cause a process to crash due to an unhandled exception (at least for us) deep in the bowels of things completely outside of our code.What happens is that the url encoded data gets choked on right here: https://github.com/apigee-127/swagger-tools/blob/master/middleware/swagger-metadata.js#L206
He changed that "%s" to "%j" and no more problems.
The text was updated successfully, but these errors were encountered: