Since the Host header is sent by a user-agent its essentially untrusted (which is why we often don't just use it). Recent versions of the Java client however do allow you to specify multiple serverNames (I think its space-delimited) and it will chose whichever one of those matches the host header.
On Thu, Apr 17, 2014 at 9:14 AM, Mathieu LARCHET < mathieu.larc...@univ-lorraine.fr> wrote: > Hi guys, > > I'm a long time user of the Java CAS filter, and I'm running into kind of > a problem. > > With every other CAS module (PHP, Apache), I can configure it without > setting the service name. In this case, it's automatically constructed from > the URL of the request. > > But with Java CAS filter, I can't do that. I have to set it explicitely, > which can be really painful when your application is accessed from > different virtual hosts. > > I think the service name (or server name) should be optional. If not > defined, the filter should construct it from the request. If defined, only > this value should be used. > > The service name is computed in the constructServiceUrl method of the > AbstractCasFilter class, and this method is final so there's no way to > sublass any filter and override it. > > Regards, > -- > You are currently subscribed to cas-dev@lists.jasig.org as: > scott.battag...@gmail.com > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-dev > -- You are currently subscribed to cas-dev@lists.jasig.org as: arch...@mail-archive.com To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev
