Anonymous | Login | Signup for a new account | 09-07-2024 16:52 PDT |
Main | My View | View Issues | Change Log | Docs |
Viewing Issue Advanced Details [ Jump to Notes ] | [ View Simple ] [ Issue History ] [ Print ] | ||||||||
ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||
0004618 | [Resin] | minor | always | 06-15-11 14:03 | 06-17-11 13:46 | ||||
Reporter | ferg | View Status | public | ||||||
Assigned To | ferg | ||||||||
Priority | normal | Resolution | fixed | Platform | |||||
Status | closed | OS | |||||||
Projection | none | OS Version | |||||||
ETA | none | Fixed in Version | 4.0.20 | Product Version | 4.0.19 | ||||
Product Build | |||||||||
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 | |||||||||
Attached Files | |||||||||
|
Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
28 total queries executed. 25 unique queries executed. |