|
Mantis - Resin
|
|||||
| Viewing Issue Advanced Details | |||||
|
|
|||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 4618 | minor | always | 06-15-11 14:03 | 06-17-11 13:46 | |
|
|
|||||
| Reporter: | ferg | Platform: | |||
| Assigned To: | ferg | OS: | |||
| Priority: | normal | OS Version: | |||
| Status: | closed | Product Version: | 4.0.19 | ||
| Product Build: | Resolution: | fixed | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | 4.0.20 | ||
|
|
|||||
| Summary: | 0004618: MovedPermanently in cluster | ||||
| Description: |
(rep by Aaron Freeman) >> 2) I don't think MovedPermanently works at the cluster level -- thinking >> >> it may only work at the host level, making this use case not possible. >> >> Can someone verify that? Any reason why it couldn't work at the cluster >> >> level in future releases? > > You can always use<host-default> to apply a rule across all virtual hosts. Interesting, I will give that a shot. > > URL dispatching is owned by the virtual host. The cluster level doesn't > > understand URLs, so it doesn't make sense to dispatch a URL in the > > cluster level. Does that mean the example, http://www.caucho.com/resin-4.0/admin/http-rewrite.xtp#Forwardbasedonhostname, [^] is fundamentally different then? Maybe it's doing something other than "dispatching" for Forward to work by MovedPermanently to not work? I can see why both wouldn't work at the cluster level and was surprised to see that example, actually, but just assumed that if Forward could work then MovedPermanently |
||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Relationships | |||||
| Attached Files: | |||||
| Notes | |||||
|
|
|||||
|
|
||||