Stylesheet Limits Of Internet Explorer 6..9

in

One of my colleagues recently discovered that our site was not functioning 100% correctly (CSS styles not being respected by the browser).  After doing some investigation he found that there is a hard limit of 4,095 rules.  (Why there were so many rules on that page is another discussion).

You can find the mention of the rule limit on the Microsoft Support site.   It states the following:

This problem occurs because the following conditions are true in Internet Explorer:

  • All style tags after the first 31 style tags are not applied.
  • All style rules after the first 4,095 rules are not applied.
  • On pages that uses the @import rule to continuously import external style sheets that import other style sheets, style sheets that are more than three levels deep are ignored.

Note: IE 10 bumps up the limit to 65,534 rules.

New Relic Goodness

in

Send deployment information directly to New Relic via HTTP.

Ever wish you knew what impact a new deployment had on your web app and when?  Trying to keep track of deployments (especially in a continuous deployment environment) can be error prone and tedious.  Why not just send those details automatically to New Relic?  You can - check it out from the New Relic site:

To notify New Relic of a deployment, you can POST to

https://rpm.newrelic.com/deployments.xml

and add the API key as a header

x-api-key: 8d00e2869400597af4a114d31789088e3724f391f287a4c

To use the API Key turn on API access in your account integration settings.

This example uses the application id.  If you were to specify the optional description, revision, changelog, and user fields, the curl command would look like this:

cURL and the Cloudinary API

in

I was looking for a way to check Exif data on images I had uploaded to Cloudinary without having to write code. Turns out that cURL works perfectly here.​ You can add whatever bits to the end of the request string that suite your needs.  I was looking for Exif.

​The following cURL command should return back to you a nice JSON response (after setting the correct cloud name, API key and API secret of your account of course):

Authentication is realized via Basic Authentication over secure HTTP. Your Cloudinary API Key and API Secret are used for the authentication.

I was unable to get the -d option of cURL to work correctly so instead I encased the entire request in a matching set of ' '.  YMMV.

​