HTTP+HTTPS server simultaneously

[helllamer]

It will be good to listen HTTP and HTTPS ports simultaneously. Current easy-to-use variant, CB + nginx as proxy, crashes on chunked encoding and other HTTP/1.1 features. This is because nginx does not support HTTP/1.1.

By now, other possible crunches are:

• CB + apache + mod_proxy + mod_ssl - it works! But have much more complexity (compared with nginx).
• Run two instances of CB in cluster: disadvantages are overhead of session replication, double RAM consumption and overall system design looks ugly.

Also, a patch was proposed some time ago.
Hope, this will be implemented in future.

Original message from google-groups.
Some related patches was in pull-request #44 "Multiple listeners".

[evanmiller]

I'm happy to have multiple listeners. I was unhappy with the previous patch set because I thought it was too complex and not re-usable enough.

Do you need to distinguish HTTP from HTTPS traffic inside the application?

[helllamer]

I think, it will be enought to:

• In controller: somehow detect, if SSL is enabled or not. It can be used to enforce SSL or plain HTTP using absolute-URL redirects.

[evanmiller]

I'm thinking something like

Req:http_or_https() -> http | https

[helllamer]

Yes, this or something like this will be enough for 99% cases.

[kotedo]

Evan,

maybe something like

protocol() -> http | https

--Kai

On Fri, Jan 25, 2013 at 9:10 AM, Evan Miller notifications@github.comwrote:

I'm thinking something like

Req:http_or_https() -> http | https

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/191#issuecomment-12704397.

[evanmiller]

@kotedo, good call since SPDY is around the corner.

[evanmiller]

Ok, I submitted a pull request to SimpleBridge, check out

nitrogen/simple_bridge#17

[ilyashuma]

Btw, i pushed some code to SimpleBridge for support of X-Forwarded-Proto header ( nitrogen/simple_bridge#32 ).

It can be useful when nginx is in charge of SSL, and cb is running behind.

[danikp]

At time of writing this comment, NGINX working fine with CB for all protocols it supports including SPDY. Also, there is ways to distinguish http and https traffic. And for all webservers' related stuff we rely on simple_bridge, so that feature should be implemented there, may be as part of nitrogen/simple_bridge#35