cancel
Showing results for 
Search instead for 
Did you mean: 
Mel-SoTSA
Active Contributor

"HTTP Status 400 – Bad Request" when someone who has registered tries to join early via webinar ID

I've tested this and confirmed when a registrant tries to join early (before webnar has started)  using the webinar ID at https://global.gotowebinar.com/join or  a link with ID appended ie https://global.gotowebinar.com/join/000-000-000  if they have already registered they get an "HTTP Status 400 – Bad Request" not the page that says "webinar is scheduled to begin this date and time, come back etc"

 

If non-registered email is used they get the (expected)  reg page.

 

I've tested 3 webinars, same result.

1 ACCEPTED SOLUTION

Accepted Solutions
Mel-SoTSA
Active Contributor

Re: "HTTP Status 400 – Bad Request" when registrant tries to join early via generic link

Reinstalling Chrome fixes problem.

So  https://global.gotowebinar.com/join/XXX-XXX-XXX does function as it always has. May it continue!

 

View solution in original post

5 REPLIES 5
AshC
Retired GoTo Contributor

Re: "HTTP Status 400 – Bad Request" when someone who has registered tries to join early via webin...

Hi @Mel-SoTSA

I'm afraid those urls are not accurate for attendees to join through.  You cannot simply add the webinar ID to the end of global.gotowebinar.com/join/ .... 

 

I can't recreate the error you posted in any browser when I use an existing, registered email and the 9-digit ID at https://www.gotomeeting.com/webinar/join-webinar

 

Or when I use the unique join link provided to me by GoToWebinar; 

https://global.gotowebinar.com/join/3123986716520575756/737895687 (note this number is must longer than the ID, and is created solely for the registrant)


Ash is a member of the LastPass Community Care Team.

Was your question answered? Please mark it as an Accepted Solution.
Was a post helpful or informative? Give it a Kudo!
Mel-SoTSA
Active Contributor

Re: "HTTP Status 400 – Bad Request" when someone who has registered tries to join early vi

Thanks AshC for trying it out.  So when you use the webnar ID at https://www.gotomeeting.com/webinar/join-webinar do get a reg page using an already registered email? Or do you get a "Come Back later, webinar has not started message"

 

And it used to be possible to join via https://global.gotowebinar.com/join/ + ID. Try it!  It comes up with a "To join a webinar, enter the webinar ID and your email address" page but the already registered get an error. This is new.

AshC
Retired GoTo Contributor

Re: "HTTP Status 400 – Bad Request" when someone who has registered tries to join early vi

Correct:  We've moved away from the standard webinar ID in the registration / join links to be more specific to that registered party and webinar type. 

 

The Join page on gotowebinar.com will work as intended, as well as the join links generated for each attendee, and also the original registration link you shared beforehand. 

 


Ash is a member of the LastPass Community Care Team.

Was your question answered? Please mark it as an Accepted Solution.
Was a post helpful or informative? Give it a Kudo!
Mel-SoTSA
Active Contributor

Re: "HTTP Status 400 – Bad Request" when someone who has registered tries to join early vi

Actually I think I've got browser problems. On other computer appended links work just like they always have, and after Firefox reinstall firefox is fine. Will try Chrome when I can afford to close windows!

I hope this functinalty does not go away! We send registrations to a landing page with a generic join link.  Great for those registering last minute.  They can get in with their email address. 

I'll let you know what I find.

Mel-SoTSA
Active Contributor

Re: "HTTP Status 400 – Bad Request" when registrant tries to join early via generic link

Reinstalling Chrome fixes problem.

So  https://global.gotowebinar.com/join/XXX-XXX-XXX does function as it always has. May it continue!