Http Tunneling

[peterlaursen]

OK .. this is probably because the ‘user agent string’ in SQLyog emulates (or “fakes”, if you like) a browser version that the hosting systems will not allow to perform specific actions (not allow it to use PHP XML-extensions, for instance). We have not updated this ‘user agent string’ for many years now, and SQLyog probaby identies itself to the webserver as an IE version shipped with an early Win XP release.

 

Some links (if you are intereted in such technicalities):

http://stackoverflow.com/questions/5125438/why-do-chrome-and-ie-put-mozilla-5-0-in-the-user-agent-they-send-to-the-server

http://whatsmyuseragent.com/

https://msdn.microsoft.com/en-us/library/hh869301(v=vs.85).aspx

 

We should probably update this, so that we identify ourselves to the webserver as IE 11 running on a desktop/laptop (not smartphone/tablet) system. However, as it is long time since we were into this, we will need to study/refresh our minds and test before we can release.  But there are good chances that we can fix in beginning of next week. The last link above seems to tell what we should do about it. 

[peterlaursen]

Please check with version 12.08 released an hour ago:

 

http://blog.webyog.com/2015/02/09/sqlyog-mysql-gui-12-08-released/

“When using HTTP-tunnel, SQLyog will identify itself to the webserver using a ‘user agent string’.  This string now identifies SQLyog as an  IE11-compatible application running on Windows 8.1. Before it was IE6 running on Windows XP. This has been reported to cause ‘denial of service’ with some hosting systems.”

[yasyn]

Hi,

 

Thank you very much for your help and for your high efficient work,  I checked and everything is fine with this new version  😀

[Author]

Posts