ticket tips and tricks Glastonbury 2024 resales

[Mark Greensmith]

3 minutes ago, scatteredscreens said:

it's just the 'holding page' as we call it. when the server is too busy dealing with requests for tickets that it won't let you on to buy one. to be honest it's fairly ok because it means you're at least hitting the server. in 2018 I just had the webpage hanging so i wasnt even getting any requests in.

Yeah I was just a bit confused testing the "refreshing limits", but you will see this page when looking for tickets anyway I was assuming.

 

I've had the webpage hanging too

Edited October 20, 2022 by Mark Greensmith

[leath02]

What does the locked page look like?

[scatteredscreens]

Just now, Mark Greensmith said:

Yeah I was just a bit confused testing the "refreshing limits", but you will see this page when looking for tickets anyway I was assuming.

Yes you will, if you see this it doesn't mean you've done anything wrong don't worry.

[Mark Greensmith]

2 minutes ago, scatteredscreens said:

Yes you will, if you see this it doesn't mean you've done anything wrong don't worry.

So if I "hit" the refresh limit, maybe through multiple sessions or just on one browser (I wish we all had the definitive answers!),  I wouldn't actually know as i'll arrive at the same holding page?

[scatteredscreens]

5 minutes ago, Mark Greensmith said:

So if I "hit" the refresh limit, maybe through multiple sessions or just on one browser (I wish we all had the definitive answers!),  I wouldn't actually know as i'll arrive at the same holding page?

that's not what im saying.

I don't really know what happens when you hit this limit, it hasn't happened to me. but you could try it yourself now by spamming f5.

[Mark Greensmith]

3 minutes ago, scatteredscreens said:

that's not what im saying.

I don't really know what happens when you hit this limit, it hasn't happened to me. but you could try it yourself now by spamming f5.

Yeah that's the page you get when spamming F5.

[scatteredscreens]

2 minutes ago, Mark Greensmith said:

Yeah that's the page you get when spamming F5.

I think the back end server at see tickets on ticket day has another mechanism for blocking too many requests but we're not actually sure how it works. It's mainly in place for bots I assume and not for individual people trying.

[leath02]

I will admit, it's been quite confusing seeing people talking about being locked out, I've never seen a locked page - just the typical holding page? Of which I thought was the normal page to be sat on and pressing F5 - least that's where I've gained access from both times I've been succsesful

[Mark Greensmith]

12 minutes ago, leath02 said:

I will admit, it's been quite confusing seeing people talking about being locked out, I've never seen a locked page - just the typical holding page? Of which I thought was the normal page to be sat on and pressing F5 - least that's where I've gained access from both times I've been succsesful

I'm glad i'm not the only one.. haha

[gfa]

13 minutes ago, leath02 said:

I will admit, it's been quite confusing seeing people talking about being locked out, I've never seen a locked page - just the typical holding page? Of which I thought was the normal page to be sat on and pressing F5 - least that's where I've gained access from both times I've been succsesful

https://glastonbury.seetickets.com/content/extras#

spam refresh on here and you'll see it

@Mark Greensmith too 🙂 

Edited October 20, 2022 by gfa

[leath02]

3 minutes ago, gfa said:

https://glastonbury.seetickets.com/content/extras#

spam refresh on here and you'll see it

@Mark Greensmith too 🙂 

yeah I swear that's just the normal holding page no? That's the one I've always ended up on once clicking on a ticket link, and then that's the page I've always sat and pressed F5 on

[scatteredscreens]

Is the 'too many refreshes/requests' just something handled on the seetickets end, effectively a marker on you (I use you as I'm unsure if it's based on an IP/MAC address/session cookie) that flags you as a bot or something? 

I really don't think it's something that's likely you're going to be hitting as a normal user on ticket day. You might be able to rapid some f5s now on a low activity page but come ticket day that page chugs and may hang each request, it has done for me.

[parsonjack]

Ok just to condense a couple of questions/answers from last few posts......

- The 'holding page' as seen above is displayed when the See server has no sessions available for you

- The 'holding page' is not a 'queue' of any sort

- The 'holding page' will refresh itself after 20 seconds but you are free to refresh it yourself as soon as it appears

- If you refresh the 'holding page' manually more than 60/minute you will be automatically directed to the same 'holding page' without making a valid request to the server - a wasted F5 therefore

- You will be redirected to the 'holding page' every time you make a subsequent refresh until your refresh rate falls below 60/second

- Here's the rub...because it's the same 'holding page' you won't know if you are genuinely getting 'busy' responses from the server, or if it's because you are over the limit.....you could therefore be wasting a lot of time and effort by mashing away on F5 without a care

- It's not clear what the limit is based upon...IP...MAC...Session etc.  While we're not certain the sound advice would be to stay within 60/minute on any single device, and if you have multiple devices try to split them across different connections, wifi, 4G etc.

 

 

[scatteredscreens]

1 minute ago, parsonjack said:

Ok just to condense a couple of questions/answers from last few posts......

- The 'holding page' as seen above is displayed when the See server has no sessions available for you

- The 'holding page' is not a 'queue' of any sort

- The 'holding page' will refresh itself after 20 seconds but you are free to refresh it yourself as soon as it appears

- If you refresh the 'holding page' manually more than 60/minute you will be automatically directed to the same 'holding page' without making a valid request to the server - a wasted F5 therefore

- You will be redirected to the 'holding page' every time you make a subsequent refresh until your refresh rate falls below 60/second

- Here's the rub...because it's the same 'holding page' you won't know if you are genuinely getting 'busy' responses from the server, or if it's because you are over the limit.....you could therefore be wasting a lot of time and effort by mashing away on F5 without a care

- It's not clear what the limit is based upon...IP...MAC...Session etc.  While we're not certain the sound advice would be to stay within 60/minute on any single device, and if you have multiple devices try to split them across different connections, wifi, 4G etc.

 

 

thanks for clearing this up.

we should call the above 60+ requests per minute the prison page for clarity 😅

[parsonjack]

5 minutes ago, scatteredscreens said:

I really don't think it's something that's likely you're going to be hitting as a normal user on ticket day. You might be able to rapid some f5s now on a low activity page but come ticket day that page chugs and may hang each request, it has done for me.

Very true....under TDay circumstances you'd be unlikely to hit the limit IF you're waiting for the response from See before going for F5 again.

[scatteredscreens]

Just now, parsonjack said:

Very true....under TDay circumstances you'd be unlikely to hit the limit IF you're waiting for the response from See before going for F5 again.

which you should be doing really, otherwise you're just refreshing mid-connection is how i've understood it.

if I get keep getting really bad hangs, like it's just not going anywhere i start to either get a vpn started or a fresh new browser i havent used on an incognito tab, but that's just my preference 

[parsonjack]

58 minutes ago, Mark Greensmith said:

So if I "hit" the refresh limit, maybe through multiple sessions or just on one browser (I wish we all had the definitive answers!),  I wouldn't actually know as i'll arrive at the same holding page?

Yes.  Exactly this.

[leath02]

Right as I thought, it's literally the same page

Just refresh 59 times a minute and it's all fine

[parsonjack]

2 minutes ago, scatteredscreens said:

which you should be doing really, otherwise you're just refreshing mid-connection is how i've understood it.

if I get keep getting really bad hangs, like it's just not going anywhere i start to either get a vpn started or a fresh new browser i havent used on an incognito tab, but that's just my preference 

I think the agreed response to an unresponsive browser, or the 'white screen of death' as it's been referred to before is to clear browser cache and all cookies, and close/reopen the browser.

[scatteredscreens]

Just now, parsonjack said:

I think the agreed response to an unresponsive browser, or the 'white screen of death' as it's been referred to before is to clear browser cache and all cookies, and close/reopen the browser.

in my scramble of 2018 i don't think i did this, i'll be sure to do it this time

[parsonjack]

Just now, leath02 said:

Right as I thought, it's literally the same page

Just refresh 59 times a minute and it's all fine

Yup....although at that rate you would likely not get a full response and *could* miss a booking page loading.

[andronnicus]

https://glastonbury.seetickets.com/Tour/Glastonbury-2023

https://glastonbury.seetickets.com/event/glastonbury-2023-deposits/worthy-farm/2500000

[scatteredscreens]

3 minutes ago, andronnicus said:

https://glastonbury.seetickets.com/Tour/Glastonbury-2023

https://glastonbury.seetickets.com/event/glastonbury-2023-deposits/worthy-farm/2500000

👀

[stuie]

5 minutes ago, andronnicus said:

https://glastonbury.seetickets.com/Tour/Glastonbury-2023

https://glastonbury.seetickets.com/event/glastonbury-2023-deposits/worthy-farm/2500000

How did you get these? 😂

[scatteredscreens]

I imagine those URLs might get changed slightly now? If not I'm definitely gonna just refresh that page 2 weeks today.