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
It seems like it was just a couple weeks ago that I was writing about the Lightroom 1.3 update and now there’s another one. Really though, there’s nothing major here. Just a few bug fixes and tweaks that some folks have experienced since updating to 1.3. Personally, I haven’t experienced any issues but I’m not running Leopard yet either. Anyway, below are the Mac/PC links if you need to download:
On a Mac 1.3.1 has no problem. Since I’m starting with my photography, I did some freebie that got more than 3k pictures in 2 months. I’ve changed about 3 times my work flow. Got from a collections main thing to a folder main thing, so I did a lot of copying inside LR. The only thing that I didn’t pass through the ringer is the hookup with PS. Since I’m not that good in PS. But this will come.
And in all that time NOT PROBLEMs what so ever.
Hey, I have a problem: when I try to “Edit in Adobe Photoshop CS3”, and select “Edit a Copy”… It doesn’t open in Photoshop CS3 a .PSD file: it opens a .JPG file.
Is that ok? Comments?
PC – Vista
So far, I have no problems
PC Vista
Matt: hey, you should add the plugin for “Notify me of followup comments via e-mail”, check this out: http://www.h4cker.cc/2007/12/11/asus-upgrades-en8800gt-cards-with-1gb-of-memory.html
I take it back. LR 1.3.1 was apparently not the cause of my troubles. Not sure what the cause of all my images appearing to have been changed in 2 different programs but it also showed up in LR 1.3. The greater problem I think is that so many of us have so little trust in Adobe getting this software right, that we automatically assume it is LR that is the cause of a problem. I have always been impressed with the power of Adobe software, but their implementation of Windows conventions leaves much to be desired.
I’m having some strange things now with 1.3.1 too . . . my develop sliders now show “M” where there was before a numerical value, and some text is invisible now . . . weird.
I loaded LR 1.3.1 and went back to 1.3. The new version was telling me that my files had been altered by both LR and an external program. When I tried to resolve using the dialog provided by LR, all the files had their Develop history re-set. Luckily, I was doing the resolve on a folder basis and not the entire catalog. I have used ACDSee on some of my files to put the original file name in the caption area but that is the only external mod I have done. I have lost weeks of development work! The reset happened using either option – save disk settings or overwrite (can’t remember the exact wording)
PC XP SP2
v1.3 affected me a lot. All of my compressed D1x NEFs were “magentized” and this happened also to some D100 users. I’m glad Adobe solved this issue quickly.