: Can CloudFlare use different origins based on path pattern? I'm trying to switch from AWS CloudFront to CloudFlare. Currently, my web site is hosted on EC2 and my large static files are placed

@Correia994

Posted in: #Cdn #Cloudflare

I'm trying to switch from AWS CloudFront to CloudFlare.

Currently, my web site is hosted on EC2 and my large static files are placed in S3 separately. CloudFront let me serve the web pages and the static files with the same domain, proxying the accesses to the corresponding location (origin) based on path patterns. i.e.

example.com/files/* => S3 example.com/* => EC2


In CloudFlare, I only found URL forwarding/redirects, which returns a 301/302 redirection to the visitor instead of serving the content directly. Is it possible to avoid the 301/302 redirect, but "mask" the origin location like CloudFront does?

I need to avoid the 301/302 redirect since a custom client application will access the static files, but the application does not support http redirection (yes, I know it's silly).

Vote Up Vote Down

Login to post a comment!