Note:
Also see my updated 2016 post about this topic.
Tomorrow is that time of year again, when hundreds of thousands of people spend hours pressing their F5 key, in an often futile attempt to try to book Glastonbury Festival tickets. Although I have been successful the last couple of years anyway, this year I had the opportunity to do a bit of investigation beforehand, as they had a smaller ticket sale on Thursday evening. Since we have baby in tow this year, will be caravanning, and couldn’t buy a coach ticket, but I could use the opportunity to check out the SeeTickets servers, and get an idea how their pages and queuing system work. This is also more important, since 15,000 of the tickets have already sold, there will be less available tomorrow than on previous years. When I first hit the site, right on the dot of 6pm, I refreshed a few times, and immediately got to the coach ticket selection page. Here, you got to choose between Wednesday, and Thursday departures. I clicked Wednesday, and immediately got a registration numbers form. I was impressed - in the past I’d been stuck in a queue for a long time before being able to type my reg numbers in! So, I saved the page, so I could have a look at it later. I clicked through, and had a look at all the pages, including the payment page. Over the next half an hour I refreshed the page a few times, until I got added to the normal queuing system. This is a javascript based refresh which refreshes every 20 seconds, and polls the server for a booking slot. I assume they use a session based queuing system, because although last year there were problems after typing in the registration numbers (because of a DNS configuration issue), the previous festival, once I got through to this screen, I had no further issues. Looking at this then, it’s fairly simple on how to get your booking slot - you keep refreshing the page until instead of showing you a queuing message, you get a page where you type in the registration numbers. What you are actually hoping the see, is this form: