We have same problem with Pound Proxy Server / Load Balancer.
But we have to fix the org.dspace.authenticate.IPAuthentication
described in JIRA https://jira.duraspace.org/browse/DS-1654
-
Jordan PIŠČANC
IR IT Manager Developer
CenTraCon-SI
http://www.centracon.units.it
Hi Elvi,
you're right that you need to configure your Apache to send the
X-Forwarded-For headers. Assuming that works on the Apache side, there
is one more modification you need to make on the DSpace side to make
DSpace look at the IP address in X-Forwarded-For rather than the
actual IP address
Dear all,
We are using apache webserver as a front end for our dspace instance. I did
this using mod_jk. Now, our server is (may be) behind a firewall/proxy/load
balancer and it is forwarding its own local ip address instead of the
user's ip address. I tried implementing this (
Hi, this is a tangent, but if you want a really handy tool for your box,
grab a copy of ipcalc (it's in most package managers):
http://jodies.de/ipcalc
I use this whenever I need to spot-check my guesses at CIDR notation.
--
HARDY POTTINGER pottinge...@umsystem.edu
University of Missouri
On Thu, Sep 12, 2013 at 06:32:45PM +0800, Nemiz, Elvi wrote:
Lastly, in
authentication-ip.cfg, what is the correct syntax for specifying ip range?
If for example our ip range is 203.xxx.xx.129 to 203.xxx.xx.142? I tried
using 203.xxx.xx.129/142 and I get Malformed *IP range* specified for
5 matches
Mail list logo