I would like to see an "Approximate Filesize" or "Filesize" feature added to the Cobalt API. This feature would provide an estimate of the filesize for given files. If it's just an approximate, it would be fine.
Originally created by @PizzaSpark on GitHub (Jul 29, 2024).
Original GitHub issue: https://github.com/imputnet/cobalt/issues/663
I would like to see an "Approximate Filesize" or "Filesize" feature added to the Cobalt API. This feature would provide an estimate of the filesize for given files. If it's just an approximate, it would be fine.
When cobalt knows the final file size, the header Content-Lenght will contain the file size.
<!-- gh-comment-id:2256806211 -->
@lostdusty commented on GitHub (Jul 29, 2024):
When cobalt knows the final file size, the header Content-Lenght will contain the file size.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @PizzaSpark on GitHub (Jul 29, 2024).
Original GitHub issue: https://github.com/imputnet/cobalt/issues/663
I would like to see an "Approximate Filesize" or "Filesize" feature added to the Cobalt API. This feature would provide an estimate of the filesize for given files. If it's just an approximate, it would be fine.
@lostdusty commented on GitHub (Jul 29, 2024):
When cobalt knows the final file size, the header Content-Lenght will contain the file size.