Author Topic: 414 Request-URI Too Long: Buffer overflow detected  (Read 8288 times)

basil2089

  • Newbie
  • *
  • Posts: 2
  • Karma: +0/-0
414 Request-URI Too Long: Buffer overflow detected
« on: October 01, 2012, 02:00:40 AM »

I've been using the Ted 5000 for almost 1 year now with little trouble. Today  I had to reset my router and when I went to the TED address, I got this error message: "
                   414 Request-URI Too Long: Buffer overflow detected"

I reset the device and the router again and I am still getting the same error.

Any ideas?

TEDSupport6

  • Sr. Member
  • ****
  • Posts: 291
  • Karma: +0/-0
Re: 414 Request-URI Too Long: Buffer overflow detected
« Reply #1 on: October 02, 2012, 11:37:15 PM »
Your Gateway's IP address has most likely changed due to resetting your router. I suggest using the installation utility to locate the new IP address.

basil2089

  • Newbie
  • *
  • Posts: 2
  • Karma: +0/-0
Re: 414 Request-URI Too Long: Buffer overflow detected
« Reply #2 on: October 04, 2012, 02:52:31 AM »
IP address is the same.  I am using Fire Fox browser when I get this message.  I've used it before with out any problems. I decided to try Internet Explorer instead and it worked!!!!  So I guess I have browser problem and not a TED 5000

jackmay52

  • Newbie
  • *
  • Posts: 1
  • Karma: +0/-0
Re: 414 Request-URI Too Long: Buffer overflow detected
« Reply #3 on: November 09, 2012, 04:13:53 AM »
Thanks for the post. I used your answer to help me get going again.
Jack

handdm

  • Newbie
  • *
  • Posts: 1
  • Karma: +0/-0
Re: 414 Request-URI Too Long: Buffer overflow detected
« Reply #4 on: March 09, 2013, 10:29:15 PM »
I came across a similar issue in Firefox., I confirmed that accurate data was still getting to external provide.   Getting to IE9 worked.

egorian

  • Newbie
  • *
  • Posts: 2
  • Karma: +0/-0
Re: 414 Request-URI Too Long: Buffer overflow detected
« Reply #5 on: April 02, 2013, 11:39:19 PM »
I suggest to try cleaning Cookies in Firefox.

pderby

  • Newbie
  • *
  • Posts: 6
  • Karma: +0/-0
Re: 414 Request-URI Too Long: Buffer overflow detected
« Reply #6 on: June 20, 2013, 02:49:00 PM »
I'm getting the same error with Safari on OS X, and Safari on IOS/iPhone 5.  However , FireFox on OS X and Chrome on OS X and IOS works just fine. Also works on Windows 7 with IE and Firefox.   Deleting Cookies on Safari OS X does not resolve the problem.

staze

  • Newbie
  • *
  • Posts: 4
  • Karma: +0/-0
Re: 414 Request-URI Too Long: Buffer overflow detected
« Reply #7 on: January 30, 2014, 12:23:05 AM »
Any update on this issue? I'm seeing this with Chrome in OS X (10.7) connecting from a domain (home.example.com:8181) where if I connect via the IP:8181, it works.

jasono

  • Newbie
  • *
  • Posts: 4
  • Karma: +0/-0
Re: 414 Request-URI Too Long: Buffer overflow detected
« Reply #8 on: February 03, 2014, 11:05:24 PM »
I was having this issue all the time. I have google analytics running on my web server and I have some general cookies _utma, _utmc, _utmz for my web site ip address. Removing the cookies fixed the issue. I think this would come back but you might want to look into the cookies. Let me know.

staze

  • Newbie
  • *
  • Posts: 4
  • Karma: +0/-0
Re: 414 Request-URI Too Long: Buffer overflow detected
« Reply #9 on: February 04, 2014, 11:28:55 PM »
Wow, yeah, really old cookie hanging around that was applying to everything on the domain. Cool.

Thanks!

jasono

  • Newbie
  • *
  • Posts: 4
  • Karma: +0/-0
Re: 414 Request-URI Too Long: Buffer overflow detected
« Reply #10 on: February 06, 2014, 10:32:14 PM »
I found this website with more details on the issue:
https://nuxx.net/blog/2011/01/19/ted-5000-g-webserver-is-a-deal-breaker/

staze

  • Newbie
  • *
  • Posts: 4
  • Karma: +0/-0
Re: 414 Request-URI Too Long: Buffer overflow detected
« Reply #11 on: February 13, 2014, 05:03:23 AM »
I found this website with more details on the issue:
https://nuxx.net/blog/2011/01/19/ted-5000-g-webserver-is-a-deal-breaker/

Yeah, i had seen that, but didn't really think it applied since there shouldn't have been a global cookie for my domain... turns out there was because it was ancient! Ah well...

Thanks!