Feature #3819

OneGate resists secure configuration

Added by Bill Cole over 4 years ago. Updated over 3 years ago.

Status:ClosedStart date:05/26/2015
Priority:NormalDue date:
Assignee:Daniel Molina% Done:

100%

Category:Core & System
Target version:Release 5.0
Resolution:fixed Pull request:

Description

OneGate cannot be configured to use HTTPS and because it answers requests for '/' with a bogus "Content-type: text/html" (should be "Content-type: application/json") the returned data is mishandled if a reverse proxy that attempts to rewrite body URIs (e.g. Apache mod_proxy_html) is used to wrap the service in TLS.

Ideally, OneGate should:

1. Either support HTTPS operation directly or support a proxy URI in its configuration to be used as the base URI when answering endpoint requests.
2. Use a HTTP Content-type header consistent with the actual data sent.

Associated revisions

Revision 88d4825b
Added by Daniel Molina almost 4 years ago

feature #3819: Add ssl proxy url to the onegate con

Revision a35b75d1
Added by Daniel Molina almost 4 years ago

feature #3819: Set content type for onegate responses

Revision 838f64d5
Added by Daniel Molina almost 4 years ago

feature #3819: Set content type for onegate responses

Revision 034f6ab8
Added by Daniel Molina almost 4 years ago

feature #3819: Add ssl proxy url to the onegate con
(cherry picked from commit 88d4825be2d48feebb210a4323e523490f0cee67)

Revision 3bc3503d
Added by Daniel Molina almost 4 years ago

feature #3819: Add ssl proxy url to the onegate con
(cherry picked from commit 88d4825be2d48feebb210a4323e523490f0cee67)

(cherry picked from commit 034f6ab8eee13a188cebd163367a4c23dc0a3dc6)

Revision 4508319e
Added by Daniel Molina almost 4 years ago

feature #3819: Set content type for onegate responses

(cherry picked from commit 838f64d5ad1eeb58b50118876e08628a82b7cf63)

History

#1 Updated by Carlos Martín over 4 years ago

  • Assignee deleted (Carlos Martín)

#2 Updated by Ruben S. Montero over 4 years ago

  • Tracker changed from Bug to Feature
  • Status changed from Pending to New
  • Assignee set to Daniel Molina
  • Target version set to Release 4.14

#3 Updated by Daniel Molina about 4 years ago

  • Assignee deleted (Daniel Molina)

#4 Updated by Ruben S. Montero about 4 years ago

  • Tracker changed from Feature to Backlog
  • Target version changed from Release 4.14 to Release 5.0

#5 Updated by Daniel Molina almost 4 years ago

  • Tracker changed from Backlog to Feature
  • Status changed from New to Closed
  • Assignee set to Daniel Molina
  • Target version changed from Release 5.0 to Release 4.14.2
  • % Done changed from 0 to 100
  • Resolution set to fixed

#6 Updated by Rolandas Naujikas almost 4 years ago

Please commit those changes into one-4.14.

#7 Updated by Daniel Molina almost 4 years ago

Cherry picked, thank you

#8 Updated by Daniel Molina almost 4 years ago

  • Target version changed from Release 4.14.2 to 82

#9 Updated by Ruben S. Montero over 3 years ago

  • Target version changed from 82 to Release 5.0

Also available in: Atom PDF