|
Mantis - Resin
|
|||||
| Viewing Issue Advanced Details | |||||
|
|
|||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 2774 | minor | always | 07-08-08 09:26 | 07-08-08 11:59 | |
|
|
|||||
| Reporter: | ferg | Platform: | |||
| Assigned To: | ferg | OS: | |||
| Priority: | urgent | OS Version: | |||
| Status: | closed | Product Version: | 3.1.6 | ||
| Product Build: | Resolution: | fixed | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | 3.2.0 | ||
|
|
|||||
| 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 |
||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Relationships | |||||
| Attached Files: | |||||
| Notes | |||||
|
|
|||||
|
|
||||