0002774: rewrite-dispatch and authenticator

Viewing Issue Simple Details [ Jump to Notes ]

[ View Advanced ] [ Issue History ] [ Print ]

Category

Severity

Reproducibility

Date Submitted

Last Update

0002774

[Resin]

minor

always

07-08-08 09:26

07-08-08 11:59

Reporter

ferg

View Status

public

Assigned To

ferg

Priority

urgent

Resolution

fixed

Status

closed

Product Version

3.1.6

Summary

0002774: rewrite-dispatch and authenticator

Description

(rep by Leonid Geller)

I have cleaned up the configuration and this is what I found:

* A simple webapp with resin-web.xml containing authentication
instructions works well when the user makes a direct request to an http
resource in that application. For example (attached) in the webapp test,
going to http://someurl/test [^] will trigger basic auth challenge as
specified.
* Going to the same app using a forward based on host name does not
trigger the auth. For example, if I have a rewrite-dispatch at the
cluster level:

<rewrite-dispatch>
<forward regexp="http://.*xml\.[^/]+" [^] target="/test/" />
</rewrite-dispatch>

I can get to the same resource by going to http://xml.foo.com/ [^] yet
this time w/o the challenge.

This is a problem for us because we are trying to combine dynamic
deployment of versioned webapps with some of them containing security
constraints.

At this point, we are just looking for a solution that would allow us to

Additional Information

Attached Files

Relationships

Notes
(0003248) ferg 07-08-08 11:59	server/1kq{0,1} Added target to <dispatch> tag.

Issue History
Date Modified	Username	Field	Change
07-08-08 09:26	ferg	New Issue
07-08-08 11:59	ferg	Note Added: 0003248
07-08-08 11:59	ferg	Assigned To	=> ferg
07-08-08 11:59	ferg	Status	new => closed
07-08-08 11:59	ferg	Resolution	open => fixed
07-08-08 11:59	ferg	Fixed in Version	=> 3.2.0

Mantis 1.0.0rc3[^]

28 total queries executed.
25 unique queries executed.