CloudFlare provides web performance and security solutions, enhancing site speed and protecting against threats.
Service URL: developers.cloudflare.com (opens in a new window)
cf_ob_info
The cf_ob_info cookie provides information on: The HTTP Status Code returned by the origin web server. The Ray ID of the original failed request. The data center serving the traffic
session
__cfseq
Sequence rules uses cookies to track the order of requests a user has made and the time between requests and makes them available via Cloudflare Rules. This allows you to write rules that match valid or invalid sequences. The specific cookies used to validate sequences are called sequence cookies.
session
cf_clearance
Whether a CAPTCHA or Javascript challenge has been solved.
session
_cfuvid
The _cfuvid cookie is only set when a site uses this option in a Rate Limiting Rule, and is only used to allow the Cloudflare WAF to distinguish individual users who share the same IP address.
session
__cflb
When enabling session affinity with Cloudflare Load Balancer, Cloudflare sets a __cflb cookie with a unique value on the first response to the requesting client. Cloudflare routes future requests to the same origin, optimizing network resource usage. In the event of a failover, Cloudflare sets a new __cflb cookie to direct future requests to the failover pool.
session
__cf_bm
Cloudflare's bot products identify and mitigate automated traffic to protect your site from bad bots. Cloudflare places the __cf_bm cookie on End User devices that access Customer sites that are protected by Bot Management or Bot Fight Mode. The __cf_bm cookie is necessary for the proper functioning of these bot solutions.
session
__cfruid
Used by the content network, Cloudflare, to identify trusted web traffic.
session
cf_chl_rc_m
These cookies are for internal use which allows Cloudflare to identify production issues on clients.
session
cf_chl_rc_ni
These cookies are for internal use which allows Cloudflare to identify production issues on clients.
session
cf_chl_rc_i
These cookies are for internal use which allows Cloudflare to identify production issues on clients.
session
__cfwaitingroom
The __cfwaitingroom cookie is only used to track visitors that access a waiting room enabled host and path combination for a zone. Visitors using a browser that does not accept cookies cannot visit the host and path combination while the waiting room is active.
session
cf_use_ob
The cf_use_ob cookie informs Cloudflare to fetch the requested resource from the Always Online cache on the designated port. Applicable values are: 0, 80, and 443. The cf_ob_info and cf_use_ob cookies are persistent cookies that expire after 30 seconds.
session
Matt thanks for this video. A huge help!!!
This makes total sense. Thank’s matt. PS if you store all your photos on one drive…do you back them up to another drive? If so, what would be the best program do automatically back them up without thinking about it?
Cheers,
Lucas.
Matt — hehe! Two days before I saw this video I was struggling to get this figured out! When I finally did, this popped in my reader! What timing! 🙂 But now I really got it all figured out!
I about filled my laptop hd and had to move most of my music/photos to my ehd. I wanted to keep just the 2011 images on my laptop, but move all of the previous years/gigs worth off my laptop all together. I noticed though that the lightroom catalog folders were several gigs of data as well, so I also moved them to my ehd. Took a bit to figure out how to reconnect them — but my question is… does it make good sense to have both the catalog folder and the images together on the same drive? Or does it make LR3 work harder to have the images and the catalogs on separate drives? Hope that makes sense! Thanks for your help!
@Michelle,
I personally don’t see a slow down, But it all depends on how fast your usb is or if you use fire wire. The only advantages to having them together is that you can connect the same EHD to another computer that has LR and add, manage your photos and when you go back to other computer all that will show up in catalog. Be sure to save XMP as side car file ( those are your adjustments info for each file ) .
I also make a back up of my catalogs once a month and store the back up on a different drive just in case of a crash or failure of HD. BUt lets also see what Matt has to say too 🙂
Ron
Hey Matt,
Thanks for sharing this; reminds me too that I need to sort out some space on my drives.
Cheers,
Glyn
Thanks for the tip but why a 6′ video when you could provide a text I can read in 30″
Phil… FYI for the future. Next time, stop your comment at “Thanks for the tip”
🙂
🙂 🙂
If your replacing the drive with a lager one, just give it the same drive letter of the old one that’s even easier. you can just copy the old drive’s content to the new one that’s larger, after your done go and change the drive letter to that letter the old drive was. of course you have to disconnect the old drive so you can. and after that your in biz. you even have the smaller drive you can format and give another drive letter to and use for something else. Kick it up a notch and have the LR catalog for the photos on that drive only also on that drive and you can take your drive to another computer that has LR on it and access you catalog for that drive,
In my case I have 2 drives One for business photos which has its own catalog and that catalog is on that drive. The second drive is for personal photos and its set up the same as the other, with its own catalog on it. I just load the catalog I want to work in when I launch LR.