Revert "Merge pull request #10069 from Turbo87/publish-stream" #10102
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This reverts PR #10069 and resolves #10098.
The 503 error returned by Heroku is apparently caused by our usage of the "legacy router" on Heroku. When using "Heroku Router 2.0" the 503 error is gone, but now AWS Cloudfront starts acting up and returns 500 errors instead.
From the looks of it this appears to be a bug in Cloudfront, which does not seem to be able to handle HTTP responses while the request hasn't fully been received yet?
Unfortunately, that means we have to revert the semi-streaming publish endpoint for now and buffer everything upfront again until we either figure out how to make this work in Cloudfront, or switch to a different CDN for the crates.io API.