Project

General

Profile

Feature #51017

rgw: beast: lack of 302 http -> https redirects

Added by Konstantin Shalygin over 1 year ago. Updated 4 months ago.

Status:
New
Priority:
High
Assignee:
-
Target version:
% Done:

0%

Source:
Community (user)
Tags:
Backport:
pacific quincy
Reviewed:
Affected Versions:
Pull request ID:

Description

With civetweb was possible to define:

port=0.0.0.0:80r+443s

This means: all requests on 80 port: return to client HTTP 302 with "Location" header: original request with https scheme

For example:

GET http://example.com/bucket/object -> 302 Location: https://example.com/bucket/object

History

#1 Updated by Konstantin Shalygin 4 months ago

  • Tracker changed from Bug to Feature
  • Priority changed from Normal to High
  • Target version set to v18.0.0
  • Backport set to pacific quincy

Also available in: Atom PDF