Bug 799235 - garbage string found when access mysql database via http
garbage string found when access mysql database via http
Product: OpenShift Origin
Classification: Red Hat
Component: Pod (Show other bugs)
Unspecified Unspecified
low Severity low
: ---
: ---
Assigned To: Krishna Raman
libra bugs
Depends On:
  Show dependency treegraph
Reported: 2012-03-02 03:15 EST by Meng Bo
Modified: 2014-06-18 03:24 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2012-03-02 13:12:23 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Meng Bo 2012-03-02 03:15:04 EST
Description of problem:
garbage string found when access mysql database via http

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.create app and embed mysql to it
rhc-create-app -a php1 -t php-5.3
rhc-ctl-app -a php1 -e add-mysql-5.1
2.ssh to the app
ssh uuid@<app>-<domain>.stg.rhcloud.com
3.try to access the mysql db via http with port number
curl http://<localip>:3306/
Actual results:
garbage string found in the output.

Expected results:
the message should be readable.

Additional info:
[php1-bmeng5s.stg.rhcloud.com ~]\> curl
 5.1.61?o6ZG1]d�^-b)CVg$xStn��Got packets out of order
Comment 1 Rob Millner 2012-03-02 13:12:23 EST
To the best of my knowledge, that is the correct behaviour.  MySQL is its own binary format.  Its header is a binary string and http to port 3306 should never produce the expected result above.

I can't find a reference in the MySQL manual for connecting http to the MySQL port.  If you can find one please re-open this request.

Note You need to log in before you can comment on or make changes to this bug.