Bug 42013 - mod_proxy in a LAN context
Summary: mod_proxy in a LAN context
Status: RESOLVED DUPLICATE of bug 45405
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: mod_proxy (show other bugs)
Version: 2.2.4
Hardware: Other other
: P2 normal (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-04-01 05:00 UTC by Nicolas Mailhot
Modified: 2018-02-25 20:25 UTC (History)
0 users


Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Nicolas Mailhot 2007-04-01 05:00:12 UTC 
When using mod_proxy on small LANs it would be nice to be able to do transparent
proxying (including on the proxy server)

ie tell the firewall/routing engine on the gateway "redirect all traffic to
selected internet ports through mod_proxy"

For this to work one needs to be able to distinguish internet traffic emitted by
mod_proxy from traffic emitted by other apps on the gateway. But right now it's
not possible to fix the source port used by mod_proxy, which kills the whole scheme
Comment 1 rahul 2008-05-30 02:05:48 UTC 
Marking this as duplicate as 44806 is asking for the same feature and it contains more information.


*** This bug has been marked as a duplicate of bug 44806 ***
Comment 2 D. Stussy 2008-10-26 13:56:25 UTC 
Bug 44805 superseded by 45405.  #45405 posted to dev mailing list this day.
Comment 3 Rainer Jung 2018-02-25 20:25:35 UTC 
Undo spam change

*** This bug has been marked as a duplicate of bug 45405 ***