-
Notifications
You must be signed in to change notification settings - Fork 315
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Error no. 1" with HTTP tunnel #1542
Comments
Comment #1 originally posted by webyog on 2010-10-31T16:31:03.000Z: also see 1177 |
Comment #2 originally posted by webyog on 2010-11-14T12:52:28.000Z: <empty> |
Comment #3 originally posted by webyog on 2011-01-05T07:17:24.000Z: Usually Error No:1 indicates the HTTP response is corrupted/incomplete/not-usable. |
Comment #4 originally posted by webyog on 2011-01-24T13:31:15.000Z: The error message is changed now Error No.1 |
Comment #5 originally posted by webyog on 2011-05-06T10:09:30.000Z: Issue not fixed. |
Comment #6 originally posted by webyog on 2011-05-16T09:11:05.000Z: Adding on to comment number 5.. It should say cant connect to MySQL server. Error 2003 needs to be popped up instead of the tunneling URL error when the MySQL server is turned off. |
Comment #7 originally posted by webyog on 2012-03-03T10:45:10.000Z: Also error 10 seems to need a more generic error message. |
Comment #8 originally posted by webyog on 2012-03-03T10:49:25.000Z: Forgot the link to last comment: |
Original issue 1542 created by webyog on 2010-10-26T19:00:06.000Z:
When SQLyog receives a HTTP-response that cannot be used/is invalid or whatever of the kind SQLyog reports "Error no. 1". This is simply too bad!
(refer Ticket # 10449 for instance - but there are more. Search Forums and tickets).
There may be several reasons (including a very old PHP version, XML issues with PHP configuration and probably much more) I do claim that we should be able to detect the exact reason in every case, but at least the error message should be rewritten like "the webserver returned an unexpected HTTP response that is not usable for SQLyog HTTP tunnel"
The text was updated successfully, but these errors were encountered: