-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Handle redirects #201
Comments
Do you have a reproducer? IIRC there is a curl option to follow redirects, but it thought it was default to on. |
It was likely a piece of content that was explicitly pointed at connect.rstudioservices.com that didn't gracefully handle when we migrated to connect.posit.it and put a redirect in place. |
An rsconnect issue from the same time (host rename): rstudio/rsconnect#760 One problem we observed is that the initial request received a redirect response but the client didn't recognize that its payload needed to be resent. This comment talks about what we saw for colorado: rstudio/rsconnect#754 (comment) |
Yeah, I believe this was related to these rstudio/pins-r#760 The problem for this post was a few scheduled reports on Connect that were not handling redirects. As a result, they just blocked and filled the job queue so nothing else on the server could run. I'll DM the reports in question. You're right though - a rudimentary check just now showed |
That sounds like https://curl.se/libcurl/c/CURLOPT_POSTREDIR.html |
We recently hit redirect issues where
connectapi
would just hang on redirects. We should handle redirects more nicely@jspiewak
The text was updated successfully, but these errors were encountered: