-
-
Notifications
You must be signed in to change notification settings - Fork 818
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 #1502
Comments
It appears package_control's downloaders handle redirects well already. Tested on ST 3143 and 4147 on Windows, running PC on python 3.3 as well as on 3.8 All of the following expressions, executed via ST's console handle 302 and download the requested file as expected. A detailed log to proove that can be found at #1416 (comment) CurlDownloaderfrom package_control.downloaders.curl_downloader import CurlDownloader;dl = CurlDownloader({"debug": True});data = dl.download("https://github.com/SublimeText/Liquid/releases/download/2.1.2/Liquid-2.1.2-st4126.sublime-package", "", 5.0, 1) UrlLibDownloaderfrom package_control.downloaders.urllib_downloader import UrlLibDownloader;dl = UrlLibDownloader({"debug": True});data = dl.download("https://github.com/SublimeText/Liquid/releases/download/2.1.2/Liquid-2.1.2-st4126.sublime-package", "", 5.0, 1) WinINetDownloaderfrom package_control.downloaders.wininet_downloader import WinINetDownloader;dl = WinINetDownloader({"debug": True});data = dl.download("https://github.com/SublimeText/Liquid/releases/download/2.1.2/Liquid-2.1.2-st4126.sublime-package", "", 5.0, 1) Are there any examples or sceanarios which are not covered by the current implementation? |
The |
Interesting finding. Maybe we should come back to wbond/package_control_channel#8050 and use your refactored reviewer via Github Actions. |
I don't see why not. Just someone needs to do it. The actions should probably be moved to some sublime-text specific repo rather than living in sublime_lsp org. |
All downloaders should handle HTTP codes 301, 302, 303 and 307.
The text was updated successfully, but these errors were encountered: