StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POretrieving the client source port on a HTTPD -> Tomcat setting
primarykey
Id
9811990
data
AcceptedAnswerId
0
AnswerCount
2
ClosedDate
CommentCount
4
CommunityOwnedDate
CreationDate
2012-03-21T20:02:57.777
FavoriteCount
0
LastActivityDate
2013-01-30T14:09:18.327
LastEditDate
2012-03-21T20:14:43.210
LastEditorUserId
13767
OwnerUserId
1284340
ParentId
0
PostTypeId
1
Score
5
ViewCount
2388
LastEditorDisplayName
text
Body
I have an httpd server configured to handle HTTPS connections and forward the connections to a Tomcat (via http or ajp) where the requests are processed. One of the requirements I have in the Tomcat server is to log the remote port number of each request. If I hit the Tomcat directly, retrieving the remote port number is straight forward and we are currently doing it using the <code>getRemotePort()</code> function (HttpServletRequest). However, since I'm doing a reverse proxy (forwarding HTTPS requests via HTTP/AJP) a new connection will be created and I'll always get the remote port (and remote IP for that matter) for the connection from my httpd server to tomcat (except when I use AJP. In this case the remote server IP info comes correctly). I've tried different configurations on httpd, like: <pre><code>ProxyPreserveHost On ProxyPass / ajp://localhost:8009/ </code></pre> or <pre><code>ProxyPreserveHost On ProxyPass / http://localhost:8081/ </code></pre> I also played a little bit with RewriteRules, but couldn't make things work. Reading httpd documentation, mod_proxy offers request header information for things like <code>X-Forwarded-Host</code>, <code>X-Forwarded-For</code>, etc. But there is no info about source port. I've <a href="http://mail-archives.apache.org/mod_mbox/httpd-bugs/200304.mbox/%3C20030401191204.13726.qmail@nagoya.betaversion.org%3E">even found a bug</a>, where apparently a <code>X-Forwarded-Port</code> attribute was added to the proxy request header, but that code doesn't seem to have made to the main line/branch. So, in summary, how can I retrieve the source port of the client (not the reverse proxy) when HTTPD is forwarding requests to Tomcat?
Tags
<tomcat><apache>
Title
retrieving the client source port on a HTTPD -> Tomcat setting
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USRafał Rawicki
UserOwnerUserId
1. USalp
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POretrieving the client source port on a HTTPD -> Tomcat setting
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 POretrieving the client source port on a HTTPD -> Tomcat setting
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 POretrieving the client source port on a HTTPD -> Tomcat setting
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.