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
Hello, i'm migrating our dspace 1.7.2 to the 3.2 version,
I have followed al the instructions on
https://wiki.duraspace.org/display/DSDOC3x/Upgrading+a+DSpace+Installation
from 1.7.x to 1.8.x and 1.8.x to 3.x but i'm having problems with dspace
index-init command, for some items it's appearing
4 matches
Mail list logo