Bug 799235 - garbage string found when access mysql database via http
Summary: garbage string found when access mysql database via http
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: OKD
Classification: Red Hat
Component: Pod
Version: 1.x
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: ---
Assignee: Krishna Raman
QA Contact: libra bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-02 08:15 UTC by Meng Bo
Modified: 2014-06-18 07:24 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-02 18:12:23 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Meng Bo 2012-03-02 08:15:04 UTC
Description of problem:
garbage string found when access mysql database via http

Version-Release number of selected component (if applicable):
stage
rhc-cartridge-mysql-5.1-0.21.5-1.el6_2.noarch

How reproducible:
always

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 http://127.9.109.129:3306/
 5.1.61?o6ZG1]d�^-b)CVg$xStn��Got packets out of order

Comment 1 Rob Millner 2012-03-02 18:12:23 UTC
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.