cloudflare

Angular attribute for HTML stream

浪尽此生 提交于 2021-01-29 06:18:32
问题 I am trying to add a video from cloudflare stream into my website. The code that cloudflare gives runs in html but when I paste the code in the html component of my angular project. I am getting the error - Error: Template parse errors: 'stream' is not a known element: 1. If 'stream' is an Angular component, then verify that it is part of this module. 2. To allow any element add 'NO_ERRORS_SCHEMA' to the '@NgModule.schemas' of this component. (" [ERROR ->] The code that works in html looks

Using Cloudflare CDN + HTTPS with Google Cloud Storage

我与影子孤独终老i 提交于 2021-01-27 23:30:22
问题 I’m trying to figure out how to get my Google Cloud Storage bucket to work with Cloudflare. I followed the steps here https://cloud.google.com/storage/docs/static-website and did the following: Added a cname record for where I want to serve my content: cdn.test.stellarguard.me -> c.storage.googleapis.com Added a cloud storage bucket for cdn.test.stellarguard.me Uploaded a file and made it public: https://storage.googleapis.com/cdn.test.stellarguard.me/logo.svg However, when I go to https:/

Cloudflare 524 error with AJAX

我是研究僧i 提交于 2021-01-27 02:45:55
问题 I'm making an ajax request to a site behind Cloudflare. After 100 seconds, I get a 524. However I'm unable to process that 524 in my Javascript as the error page is served directly by Cloudflare and does not contain the required Access-Control-Allow-Origin headers. I wish to retry the query in the event of getting a 524. 回答1: If you know that CloudFlare edge will wait for a HTTP response from the server for exactly 100 seconds, then you could just setup a timeout equal to 100 seconds on the

Cloudflare 524 error with AJAX

江枫思渺然 提交于 2021-01-27 02:45:19
问题 I'm making an ajax request to a site behind Cloudflare. After 100 seconds, I get a 524. However I'm unable to process that 524 in my Javascript as the error page is served directly by Cloudflare and does not contain the required Access-Control-Allow-Origin headers. I wish to retry the query in the event of getting a 524. 回答1: If you know that CloudFlare edge will wait for a HTTP response from the server for exactly 100 seconds, then you could just setup a timeout equal to 100 seconds on the

Workaround for Heroku no longer supporting SSL behind Cloudflare (“Strict TLS in CDN not supported”)?

*爱你&永不变心* 提交于 2021-01-26 03:53:10
问题 A few days ago we received the error "Strict TLS in CDN not supported" on 1 Heroku app that's behind Cloudflare's proxy (orange cloud, if you know Cloudflare). Basically, client requests to https://foo.example.com are proxied through Cloudflare, who then make the requests to https://foo.herokuapp.com, caches the response, and passes the result back to the client. Notice that the entire chain is over HTTPS. We've configured Clouflare to only communicate with the end server over HTTPS, and we

Workaround for Heroku no longer supporting SSL behind Cloudflare (“Strict TLS in CDN not supported”)?

纵饮孤独 提交于 2021-01-26 03:52:53
问题 A few days ago we received the error "Strict TLS in CDN not supported" on 1 Heroku app that's behind Cloudflare's proxy (orange cloud, if you know Cloudflare). Basically, client requests to https://foo.example.com are proxied through Cloudflare, who then make the requests to https://foo.herokuapp.com, caches the response, and passes the result back to the client. Notice that the entire chain is over HTTPS. We've configured Clouflare to only communicate with the end server over HTTPS, and we

What is the difference in accessing Cloudflare website using ChromeDriver/Chrome in normal/headless mode through Selenium Python

你说的曾经没有我的故事 提交于 2021-01-21 05:15:37
问题 I have a question about --headless mode in Python Selenium for Chrome. Code from selenium import webdriver from selenium.webdriver.common.desired_capabilities import DesiredCapabilities CHROME_DRIVER_DIR = "selenium/chromedriver" chrome_options = webdriver.ChromeOptions() caps = DesiredCapabilities().CHROME chrome_options.add_argument("--disable-dev-shm-usage") chrome_options.add_argument("--remote-debugging-port=9222") chrome_options.add_argument("--headless") # Runs Chrome in headless mode.

Websocket Cloudflare with Nginx 520 error

我是研究僧i 提交于 2021-01-07 02:13:56
问题 I am jumping in on a project with some socket issues over SSL and Cloudflare... I know.. I have read about 50 different stack overflow posts and 200 blog posts to try to figure this out. The project works on my local dev server/computer just fine... I think I am on the right track - But could use some help/pointers if ya'll can. First, I thought it was weird that the /socket-io/ proxy_pass was at port 6379, the same as redis... Maybe it should be? When this was set at 6379, the socket

Websocket Cloudflare with Nginx 520 error

一曲冷凌霜 提交于 2021-01-07 02:10:23
问题 I am jumping in on a project with some socket issues over SSL and Cloudflare... I know.. I have read about 50 different stack overflow posts and 200 blog posts to try to figure this out. The project works on my local dev server/computer just fine... I think I am on the right track - But could use some help/pointers if ya'll can. First, I thought it was weird that the /socket-io/ proxy_pass was at port 6379, the same as redis... Maybe it should be? When this was set at 6379, the socket

Websocket Cloudflare with Nginx 520 error

孤人 提交于 2021-01-07 02:10:13
问题 I am jumping in on a project with some socket issues over SSL and Cloudflare... I know.. I have read about 50 different stack overflow posts and 200 blog posts to try to figure this out. The project works on my local dev server/computer just fine... I think I am on the right track - But could use some help/pointers if ya'll can. First, I thought it was weird that the /socket-io/ proxy_pass was at port 6379, the same as redis... Maybe it should be? When this was set at 6379, the socket