Bug 1053067

Summary: Can't access application via http (https works)
Product: OpenShift Online Reporter: ryan.hd.ren <ryan.hd.ren>
Component: UnknownAssignee: Dan McPherson <dmcphers>
Status: CLOSED NOTABUG QA Contact:
Severity: high Docs Contact:
Priority: unspecified    
Version: 2.xCC: libra-bugs, ryan.hd.ren
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Windows   
URL: https://wechat-ryanhd.rhcloud.com/a
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Build Name: 18397, User Guide-null-1.0 Build Date: 27-11-2013 17:29:00 Topic ID: 23153-560515 [Latest]
Last Closed: 2014-02-24 13:59:05 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Tomcat config file none

Description ryan.hd.ren@gmail.com 2014-01-14 16:13:46 UTC
Created attachment 850024 [details]
Tomcat config file

Title: Can't access application via http (https works)

Describe the issue:

Hi, I'm fresh here and tried to build a application based on Tomcat 7. Everything is perfect except for the port. I have a need to use 80 port for http, but currently my application must be accessed by https. When I try to connect with http, it always returns status aborted.

I've checked Tomcat server.xml, it correctly listens to 8080 and redirect to 8443, have attached it for ur reference.

This is very strange and conflict with User Guide 7.6 .

Hope to hear from you soon.


Suggestions for improvement:


Additional information: 

1. My application is interacting with an external system, which only supports http.

2. If I enable the port forwarding feature and access the app from local 8080, it's also fine.

Comment 2 ryan.hd.ren@gmail.com 2014-01-15 01:33:51 UTC
Not sure my application url is known to you: https://wechat-ryanhd.rhcloud.com/a

Comment 3 Luke Meyer 2014-02-24 13:49:49 UTC
Sorry, I don't think this was really a User Guide issue. Should have been sent to a different component. Docs people don't really follow up on user problems...

Visiting the application URL, it appears to be working at http or https. Let us know if there's still a problem here.

Comment 4 ryan.hd.ren@gmail.com 2014-02-24 13:59:05 UTC
Hi Luke,

Thanks for reviewing. It's a problem of the state fire wall.. sorry for put it here.