We get redirected to lularoe queue,
108.59.45.7:443
https://build.mylularoe.com/loginhttps://lularoe.queue-it.net/?
c: lularoe
e: disneynov17
ver: v3-aspnet-3.2.0
cver: 28
t: http://build.mylularoe.com/loginWe get a cookie containing our queue id
52.49.237.127:443
https://lularoe.queue-it.net/?
c: lularoe
e: disneynov17
ver: v3-aspnet-3.2.0
cver: 28
t: http://build.mylularoe.com/loginhttp://lularoe.queue-it.net/?
c:lularoe
e:disneynov17
ver:v3-aspnet-3.2.0
cver:28
t:http://build.mylularoe.com/login
[
Queue-it=u=3ab2c51c-b242-49c8-a217-36c5917cecd9;
domain=queue-it.net;
expires=Thu, 22-Nov-2018 18:21:55 GMT;
path=/;
HttpOnly
]Using that cookie and switching to http this is probably where we get redirected to the waiting page
52.49.237.127:80
http://lularoe.queue-it.net/?
c: lularoe
e: disneynov17
ver: v3-aspnet-3.2.0
cver: 28
t: http://build.mylularoe.com/login
[
Queue-it=u=3ab2c51c-b242-49c8-a217-36c5917cecd9
]http://lularoe.queue-it.net/afterevent.aspx?
c:lularoe
e:disneynov17
t:http://build.mylularoe.com/login
cid:en-USIn this case we got redirected to an after event page which gives us our queueittoken and some cookie that I don't understand
52.49.237.127:80
http://lularoe.queue-it.net/afterevent.aspx?
c:lularoe
e:disneynov17
t:http://build.mylularoe.com/login
cid:en-US
[
Queue-it=u=3ab2c51c-b242-49c8-a217-36c5917cecd9
]http://build.mylularoe.com/login?
queueittoken:
e_disneynov17~
q_00000000-0000-0000-0000-000000000000~
ts_1511375096~
ce_true~
rt_afterevent~
h_546eda205ca80eff9c39ed77fb04d476c7a20d49b6764af786444f4f34e5b4bb4af786444f4f34e5b4bb
[
Queue-it-lularoe_____________disneynov17=
Cid=en-US&
f=0;
expires=Thu, 23-Nov-2017 06:21:56 GMT;
path=/
]Immediently shifts us back to https
108.59.45.7:80
http://build.mylularoe.com/login?
queueittoken:
e_disneynov17~
q_00000000-0000-0000-0000-000000000000~
ts_1511375096~
ce_true~
rt_afterevent~
h_546eda205ca80eff9c39ed77fb04d476c7a20d49b6764af786444f4f34e5b4bbhttps://build.mylularoe.com/login?
queueittoken:
e_disneynov17~
q_00000000-0000-0000-0000-000000000000~
ts_1511375096~
ce_true~
rt_afterevent~
h_546eda205ca80eff9c39ed77fb04d476c7a20d49b6764af786444f4f34e5b4bbTrades in our queueittoken for the QueueITAccepted cookie which is what we really want, and tells us to go back to our original target
108.59.45.7:443
https://build.mylularoe.com/login?
queueittoken:
e_disneynov17~
q_00000000-0000-0000-0000-000000000000~
ts_1511375096~
ce_true~
rt_afterevent~
h_546eda205ca80eff9c39ed77fb04d476c7a20d49b6764af786444f4f34e5b4bbhttp://build.mylularoe.com/login
[
QueueITAccepted-SDFrts345E-V3_disneynov17=
IsCookieExtendable=True&
Hash=66303646dc6f65f10d25ff4bcd6a0375414e58dbf78c1f3aebba8a3a97bdf382&
Expires=1511376116&
QueueId=00000000-0000-0000-0000-000000000000;
expires=Thu, 23-Nov-2017 18:21:56 GMT;
path=/;
HttpOnly
]Immediently shifts us back to https
108.59.45.7:80
http://build.mylularoe.com/login
[
QueueITAccepted-SDFrts345E-V3_disneynov17=
IsCookieExtendable=True&
Hash=66303646dc6f65f10d25ff4bcd6a0375414e58dbf78c1f3aebba8a3a97bdf382&
Expires=1511376116&
QueueId=00000000-0000-0000-0000-000000000000;
]https://build.mylularoe.com/loginWe finially get the page we wanted They replace our QueueITAccepted token for one that will actually last a while They also give us a verification token (I have no idea what it does)
108.59.45.7:443
https://build.mylularoe.com/login
[
QueueITAccepted-SDFrts345E-V3_disneynov17=
IsCookieExtendable=True&
Hash=66303646dc6f65f10d25ff4bcd6a0375414e58dbf78c1f3aebba8a3a97bdf382&
Expires=1511376116&
QueueId=00000000-0000-0000-0000-000000000000;
]!!THE ACTUAL PAGE!!
[
QueueITAccepted-SDFrts345E-V3_disneynov17=
IsCookieExtendable=True&
Hash=7fd8ceebd6cd19a1ee55766dce70d6a861b4b2c782b4fa95b90d5548831f1ccf&
Expires=1511376117&
QueueId=00000000-0000-0000-0000-000000000000;
expires=Thu, 23-Nov-2017 18:21:57 GMT;
path=/;
HttpOnly
__RequestVerificationToken=jzw0wOipzKUcJHI2LvLOVhJr9e9POBtDDONLb7DaBLL6ydq5RKdgt4UkgCG0pgBXdKApKRRoWniI7EGSFsTg6ggUDMU1;
path=/;
HttpOnly
]