Welcome to Comcast Help & Support Forums
Find solutions, share knowledge, and get answers from customers and experts

New to the Community? Start here.

5,806,098

members

38

online now

1,952,303

discussions

Top

Error 413 on Matrix Revolutions

ANSWERED
New Poster

Error 413 on Matrix Revolutions

No problem with the previous Matrix movies.  Getting error 413 every time I try to watch it on demand (watching it on my laptop).  Please help.  Thanks.

Accepted Solution

Re: Error 413 on Matrix Revolutions

Thanks for your quick response!

 

Deleting the cookies and clearing my cache did not work.  But that gave me an idea - I simply logged out and then logged back in, then there were no more errors.

View answer in context
Tags (1)
Official Employee

Re: Error 413 on Matrix Revolutions


gstritter wrote:

No problem with the previous Matrix movies.  Getting error 413 every time I try to watch it on demand (watching it on my laptop).  Please help.  Thanks.


I cannot find issues with any Matrix movie; even Revolutions.

 

Try deleting your cookies and cache and then try again.

 

Thanks,
Joe
XfinityTV.com/Xfinity.com Support
Twitter: @XfinityTVJoe




Community Icon
I am an Official Comcast Employee.
Official Employees are from multiple teams within Comcast: Product, Support, Leadership.
We ask that you post publicly so people with similar questions may benefit from the conversation.

Was your question answered? Mark it as an accepted solution!solution Icon
Community Icon
I am an Offical Comcast Employee.
Official Employees are from multiple teams within Comcast.
We ask that you post publicly so people with similar questions may benefit.
Was your question answered? Mark it as an accepted solution!solution Icon
Community Icon
I am a Comcast Employee.
Please post so people with similar questions may benefit.
Was your question answered?
Mark it as a solution!solution Icon
New Poster

Re: Error 413 on Matrix Revolutions

Thanks for your quick response!

 

Deleting the cookies and clearing my cache did not work.  But that gave me an idea - I simply logged out and then logged back in, then there were no more errors.

Discussion stats
  • 2 replies
  • 733 views
  • 0 kudos
  • 2 in conversation