1
8
Fork
You've already forked nup
0

Consider using signed Cloud Storage URLs #3

Open
opened 2021年02月08日 13:25:02 +01:00 by derat · 2 comments
derat commented 2021年02月08日 13:25:02 +01:00 (Migrated from github.com)
Copy link

It might be nice if there were some way to create a temporary signed URL for an MP3 file so it can be shared. See https://cloud.google.com/storage/docs/access-control/signed-urls for more info.

It might be nice if there were some way to create a temporary signed URL for an MP3 file so it can be shared. See https://cloud.google.com/storage/docs/access-control/signed-urls for more info.

I don't have much interest in this. I'm not going to add Chromecast support (#9) and I already added support for read-only, rate-limited guest users (#50).

I don't have much interest in this. I'm not going to add Chromecast support (#9) and I already added support for read-only, rate-limited guest users (#50).

Right now, I'm billed App Engine's ridiculous 0ドル.12/GiB egress on days when I play a lot of music. It might be possible to avoid this by making the server's /song endpoint generate a signed URL for the GCS object and then issue a 302 redirect to it.

On the other hand, I'm not sure that this will help. GCS Coldline looks like it currently costs 0ドル.01 per 1,000 Class B operations (which include storage.*.get) and 0ドル.02 per GiB of retrieval. https://cloud.google.com/storage/pricing makes it sound like I'll still be paying at least 0ドル.12/GiB for outbound networking (excluding Asia and Australia, which are even more expensive), and I'm not sure if the "Always Free" allowance covers any of this or if it's just for data transfer within Google:

Data transfer: 100 GB from North America to each Google Cloud Data transfer destination (Australia and China excluded)

I'd also need to double-check that GCS handles range requests properly and that the URL expiry is long enough.

Right now, I'm billed App Engine's ridiculous 0ドル.12/GiB egress on days when I play a lot of music. It might be possible to avoid this by making the server's `/song` endpoint generate a signed URL for the GCS object and then issue a 302 redirect to it. On the other hand, I'm not sure that this will help. GCS Coldline looks like it currently costs 0ドル.01 per 1,000 Class B operations (which include `storage.*.get`) and 0ドル.02 per GiB of retrieval. <https://cloud.google.com/storage/pricing> makes it sound like I'll still be paying at least 0ドル.12/GiB for outbound networking (excluding Asia and Australia, which are even more expensive), and I'm not sure if the "Always Free" allowance covers any of this or if it's just for data transfer within Google: > Data transfer: 100 GB from North America to each Google Cloud Data transfer destination (Australia and China excluded) I'd also need to double-check that GCS handles range requests properly and that the URL expiry is long enough.
derat changed title from (削除) Support creating signed URLs (削除ここまで) to Consider using signed Cloud Storage URLs 2026年03月17日 14:43:10 +01:00
Sign in to join this conversation.
No Branch/Tag specified
main
headless
picture
datastore
No results found.
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
derat/nup#3
Reference in a new issue
derat/nup
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?