Following the success of my solo exhibition at Cafe Seventy Nine in Primrose Hill last year, an exhibition of my photos is now on at Oliver’s Village Cafe, Belsize, London. All prints are pure iPhoneography/mobile photography.
A client arranged penetration testing in order to achieve PCI compliance and it was found that not all cookies contained the HttpOnly flag, which is an automatic fail because apparently you are more vulnerable to XSS attacks if you don’t set your cookies to use HttpOnly.
This problem turned out to be caused by the HAProxy load balancer not adding HttpOnly to its persistence (sticky session) cookies, so I checked the HAProxy manual and did some googling, but I couldn’t find any way of making HAProxy’s persistence cookies add the HttpOnly flag.
The HAProxy website says “if you want to suggest a useful feature, please discuss it on the mailing list” so I’ve tried to do just that but have not had any response yet. In the meantime, I’ve modified the code myself so that the HttpOnly flag is added to all persistence cookies. For version 1.4.21 of HAProxy, patching src/proto_http.c with the following will add my modification to achieve this:
5348a5349,5350 > len += sprintf(trash+len, "; HttpOnly"); >
Hopefully this is something the HAProxy developers will add permanently as an option, otherwise it’s quite awkward for HAProxy users needing to pass compliance tests whilst using persistence cookies.
Edit: Willy, the developer of HAProxy, has replied on the mailing list to indicate that he’ll be adding an ‘httponly’ option to the ‘cookie’ parameter in version 1.5 of HAProxy, so that’s great news. In the meantime, my little hack above can be used for those needing HttpOnly on version 1.4.
Edit: This has now been added as an option in version 1.4.22 of HAProxy.
(This post assumes a PostgreSQL installation located at /var/lib/pgsql on a Red Hat-type Linux system such as Red Hat Enterprise Linux or CentOS. If your system differs from this, you may need to modify some of the paths accordingly.)
In PostgreSQL, sorts larger than a certain size will get performed on disk instead of in memory, and this makes them much slower as a result. Ideally all sorts should be done in memory (except for the ones that are genuinely too big to fit into your available RAM, because swapping to virtual memory should be avoided at all costs).
For six weeks I am exhibiting my iPhone photography in Cafe Seventy Nine in Primrose Hill, London.
I’ve written an article for Digital Photographer magazine called A Beginner’s Guide to iPhone Photography, which will hopefully come in useful for all you budding iPhoneographers out there. There’s a link to Part 2 at the bottom of Part 1. Enjoy!
My experience with Lion so far has been, to say the least, mixed. I thought I’d list some of my experiences in the form of a brief review.
Photographers are increasingly embracing smartphones, and Apple’s iPhone in particular, as valid alternatives to their SLRs. Adopting the philosophy that ‘the best camera is the one that’s with you’, photographers find with iPhones that they can simply point and shoot in situations where photography would not be an option with a larger camera. For many, this embodies the true essence of photography, in which making a timely visual capture of a particular moment is more important than painstakingly changing lenses and altering aperture settings. More and more photographers are questioning the assumption that bulky, costly photographic equipment is necessary for taking worthwhile photographs. Instead, they are realising that you can never tell when inspiration is going to strike, and being able to take photographs instantly at any time is incredibly advantageous.
At 7pm on 11th July, the Apple Store on Regent Street will be hosting an iPhoneography event to highlight four talented members of the London iPhoneography Group who will be showing their work and discussing how they use their iPhones for street photography in London: Daniel Holland, Robson Santos, Matthew Burlem and Leyla Bile.
Following our successful migration to Amazon’s S3 service for media storage and delivery, we decided to move our entire server infrastructure from its traditional data centre colocation to Amazon’s Elastic Compute Cloud (or ‘EC2′). Using this cloud-based infrastructure instead of data centre colocation provides two main benefits for us.