cloudflare

How to prevent exposing origin IP address on Cloudflare?

£可爱£侵袭症+ 提交于 2019-12-04 23:09:39
On Cloudflare DNS setting page it state that An A, AAAA, CNAME, or MX record is pointed to your origin server exposing your origin IP address. I have an MX record on my domain pointing to mail.mydomain.com . I believe it is something needed for the mail to work. How can I prevent it from exposing my origin IP address? CloudFlare forwards your traffic through their network by replacing the IP in DNS records with CloudFlare's IP. This process works well in all situation except mail servers. CloudFlare does not offer any service for forwarding mail and as such when you take a MX record and point

Cloudflare's Rocket Loader + Wordpress -> Ignore scripts?

こ雲淡風輕ζ 提交于 2019-12-04 17:20:59
I'm trying to make Cloudflare's Rocket Loader work on my WP site. Everything works fine except for the WP Visual Editor. I followed the advice here but it doesn't work: How do I add custom attributes to javascript tags in Wordpress? Cloudflare says that in order to make Rocket Loader ignore a javascript file I need to add the data-cfasync="false" tag before my script: <script data-cfasync="false" src="/javascript.js"></script> https://support.cloudflare.com/entries/22063443--How-can-I-have-Rocket-Loader-ignore-my-script-s-in-Automatic-Mode- Rocket loader doesn't ignore my JS files. Here's my

Preventing Abuse: Cloud Functions for Firebase

笑着哭i 提交于 2019-12-04 17:09:26
What is the best way to stop an attacker from triggering a Cloud Function repeatedly, causing a huge bill or causing the project to run into quota limits? Some ideas: Use RTDB or Cloud Storage triggers as much as possible, since writes to those are protected by those products' security rules Put functions behind a service like Cloudflare Set up billing alerts , so a notification is sent if the monthly bill is unusually large johnozbay Check my answer here . Short breakdown of items from my answer : Limit the type of requests Authenticate if you can Check for origin Use a load balancer in

S3 with Cloudflare disallow direct access

可紊 提交于 2019-12-04 11:21:33
问题 I am trying to have Cloudflare to act as CDN for files hosted on S3, in a way that nobody can access the files directly. For example: S3 bucket: cdn.mydomain.com.s3.amazonaws.com CDN (Cloudflare): cdn.mydomain.com What I want is to be able to access cdn.mydomain.com/file.jpg (Cloudflare) but not cdn.mydomain.com.s3.amazonaws.com/file.jpg (S3). Right now I have a CNAME configured on Cloudflare that points to my bucket, and the following CORS: <?xml version="1.0" encoding="UTF-8"?>

Google Maps API 3 referrerNotAllowedMapError

拜拜、爱过 提交于 2019-12-04 09:54:49
I'm no stranger to Google Maps APi, and have used it for years...but I am stumped. I've installed an exact copy of the latest code sample from Google Maps Javascript API: Simple Map. I then confirmed both my browser and server keys from Google Developers Console, added the refer two different ways(see below). Code works when I set the referer to * wildcard in console, but cannot use that in production. Here's the skinny: tested using latest example code from Google Maps API Javascript (Simple Map) YOURAPIKEYHERE - replaced with an active browser key from my account referer was tried as both *.

Cache-Control Headers not respected on CloudFlare

為{幸葍}努か 提交于 2019-12-04 07:03:28
I am trying to get some html pages to be cached, the same way images are automatically cached via CloudFlare but I can't get CloudFlare to actually hits its cache for html. According to the documentation (Ref: https://support.cloudflare.com/hc/en-us/articles/202775670-How-Do-I-Tell-CloudFlare-What-to-Cache- ), it's possible to cache anything with a Cache-Control set to public with a max-age greater than 0. I've tried various combinations of headers on my origin Nginx server without success. From a simple Cache-Control: public, max-age=31536000 to more complex headers including s-maxage

Getting com.google.gwt.user.client.rpc.StatusCodeException: 0 in GWT

▼魔方 西西 提交于 2019-12-03 12:32:31
I sometimes/often get this Exception in GWT but don't know why: SEVERE: com.google.gwt.user.client.rpc.StatusCodeException: 0 java.lang.RuntimeException: com.google.gwt.user.client.rpc.StatusCodeException: 0 at Unknown.java_lang_RuntimeException_RuntimeException__Ljava_lang_Throwable_2V(Unknown Source) at Unknown.de_ctech24_simplynews_web_client_util_SimpleCallback_$onFailure__Lde_ctech24_simplynews_web_client_util_SimpleCallback_2Ljava_lang_Throwable_2V(Unknown Source) at Unknown.com_google_gwt_user_client_rpc_impl_RequestCallbackAdapter_$onResponseReceived__Lcom_google_gwt_user_client_rpc

Cache-Control Headers not respected on CloudFlare

匿名 (未验证) 提交于 2019-12-03 08:48:34
可以将文章内容翻译成中文,广告屏蔽插件可能会导致该功能失效(如失效,请关闭广告屏蔽插件后再试): 问题: I am trying to get some html pages to be cached, the same way images are automatically cached via CloudFlare but I can't get CloudFlare to actually hits its cache for html. According to the documentation (Ref: https://support.cloudflare.com/hc/en-us/articles/202775670-How-Do-I-Tell-CloudFlare-What-to-Cache- ), it's possible to cache anything with a Cache-Control set to public with a max-age greater than 0. I've tried various combinations of headers on my origin Nginx server without success. From a simple Cache-Control: public, max-age

Is it possible to increase CloudFlare time-out?

蓝咒 提交于 2019-12-03 08:29:34
问题 Is it possible to increase CloudFlare's time-out? If yes, how? My code takes a while to execute and I wasn't planning on Ajaxifying it the coming days. 回答1: No, CloudFlare only offers that kind of customisation on Enterprise plans. CloudFlare will time out if it fails to establish a HTTP handshake after 15 seconds. CloudFlare will also wait 100 seconds for a HTTP response from your server before you will see a 524 timeout error. Other than this there can be timeouts on your origin web server.

S3 with Cloudflare disallow direct access

好久不见. 提交于 2019-12-03 07:21:01
I am trying to have Cloudflare to act as CDN for files hosted on S3, in a way that nobody can access the files directly. For example: S3 bucket: cdn.mydomain.com.s3.amazonaws.com CDN (Cloudflare): cdn.mydomain.com What I want is to be able to access cdn.mydomain.com/file.jpg (Cloudflare) but not cdn.mydomain.com.s3.amazonaws.com/file.jpg (S3). Right now I have a CNAME configured on Cloudflare that points to my bucket, and the following CORS: <?xml version="1.0" encoding="UTF-8"?> <CORSConfiguration xmlns="http://s3.amazonaws.com/doc/2006-03-01/"> <CORSRule> <AllowedOrigin>*</AllowedOrigin>