Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Imagine the following setup:

Drawio
baseUrlhttps://ceptor.atlassian.net/wiki
diagramNamerequestflow.drawio
tempPreviewrequestflow.png
width500
zoom1
pageId478347882
custContentId1030553639
lbox1
contentVer1
height500
revision1

Here, a client wants to call an application - it does that by calling theĀ Ceptor Gateway which is a reverse proxy that all requests travel through. Ceptor gateway then typically starts by establishing a session if not already present, and then examines the request information - it looks at attributes like hostname, URL Path and/or query parameters - based upon these attributes, and the configuration of the gateway, it selects a destination to transmit the request to.

...

Inside the gateway, a number of steps are performed, the actual steps vary, but typically it is similar to this:

Drawio
baseUrlhttps://ceptor.atlassian.net/wiki
diagramNameflow2.drawio
tempPreviewflow2.png
width500
zoom1
pageId478347882
custContentId1029799965
lbox1
contentVer1
height500
revision1

Listener

Requests are received via a Listener - the listener listens for incoming requests using one of the protocols HTTP, HTTPS or AJP - the configuration for the listener also decides SSL/TLS settings, and decides if the user should be prompted for a client certificate. A gateway can have multiple different listeners on any combination of IP address and port.

...