The error is typically not caused by Mediacast itself, nor is it an indication that the site is down. Instead, it occurs when your browser has accumulated too much website data (known as "cookies") from visiting various SMU websites over time.
Many SMU websites share the same parent domain (.smu.edu.sg). As you browse across different SMU systems and websites, your browser stores cookies from these sites. For most users, this does not create an issue. However, staff and faculty members, who frequently access a larger number of SMU websites and services, may gradually accumulate more cookies than the system can comfortably process.
When the amount of stored cookie data becomes too large, some platforms may reject the browser request and display a 400 Bad Request error. Mediacast, which is powered by Kaltura, appears to be more sensitive to large cookie sizes and therefore may encounter this issue sooner than other websites.
Who is affected?
This issue is generally limited to SMU staff and faculty members who regularly access many SMU systems and websites. It is unlikely to affect members of the public, as they typically do not visit enough SMU services to accumulate the same amount of browser data.
How can I resolve the issue?
The issue can usually be resolved by clearing the browser cookies associated with the affected site. While clearing the entire browser cache and cookies will also fix the problem, this may sign you out of other websites and services.
To minimise disruption, we recommend clearing cookies specifically for mediacast.smu.edu.sg (or relevant SMU sites) instead of clearing your entire browser history. Instructions can be provided for supported browsers if needed.
Longer-term context
As SMU operates a large number of websites under the smu.edu.sg domain, browser cookie accumulation can increase over time. While this issue does not affect most users, it can occasionally impact frequent users of SMU systems. IITS is actively reviewing how cookies are used across SMU websites and working with system owners to reduce unnecessary cookie usage where possible. The goal is to streamline the way websites utilise cookies, minimise cookie accumulation across the shared domain, and reduce the likelihood of cookie bloat-related issues in the future.
Related article: