16.9.8 Exploring Pre-Authenticated Requests
Compare ways to serve object bucket files, including application proxy pages and pre-authenticated request URLs.
When your application pages reference images or other assets from the object bucket by URL, you have multiple options:
- An authenticated application page can serve inline images from the bucket, or
- You can use a pre-authenticated request (PAR) URL to the bucket file.
Using the first strategy, your application page acts as a proxy to the bucket file. In the second approach, the browser downloads the file directly from the object bucket. A hybrid strategy can serve images using a local cache table of PAR URLs, encapsulating the details of using cached PAR URLs or creating new ones as necessary.
- Understanding Object Bucket Visibility
Understand when to use public or private object buckets and how your app accesses private files. - Creating Pre-Authenticated Requests
Create short-lived pre-authenticated request URLs so clients can access private bucket files directly. - Using Pre-Authenticated Requests
Use cached PAR URLs to let OCI serve private bucket images directly when possible.
Parent topic: Using an OCI Object Bucket for Files