Very Unusual Custom URL Behavior

LiveWhale
1

We have two events with custom URLs:

https://events.uconn.edu/marine-sciences-department/event/1314530

As far as I can tell, the custom URLs are configured correctly in the backend and the two events are live/published.

When I view the events on our events site: UConn Calendar, and click an event, I am taken to the event at the custom URL without issue.

When I navigate to the custom URL in another context (ex. type it directly into my browser in incognito mode or click on the link in an email), the events website loads sans an event information.

When the link works as expected, I notice that the header Request URL is a GET https://events.uconn.edu/live/calendar/view/event/slug/1296359, returning 200. When the link fails, the header Request URL is a GET https://events.uconn.edu/live/calendar/view/event/event_id/1296359, returning a 403 Forbidden.

I do not know why the behavior of custom URLs would be different in different contexts nor how to remedy it. I didn’t set up these events so are there any best practices to follow? Any insight would be great, thank you!

2

Hi Janet,

I see what you mean. That is odd and not what we’d expect. We’re taking a closer look and let you know what we find.

Thanks
Rachael

3

Hi @janet.vamos

I believe we have these two events working now—it seems like this was an edge case scenario with a customized URL.

If anyone else happens to have a similar issue, we believe resaving the event with a new slug should load the event as expected.

Hope that helps!
Rachael