Anonymous | Login | Signup for a new account | 11-22-2024 05:33 PST |
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 | |||||||
0003931 | [Hessian] | minor | always | 03-08-10 09:21 | 03-08-10 09:21 | |||||||
Reporter | ferg | View Status | public | |||||||||
Assigned To | ||||||||||||
Priority | normal | Resolution | open | Platform | ||||||||
Status | new | OS | ||||||||||
Projection | none | OS Version | ||||||||||
ETA | none | Fixed in Version | Product Version | 4.0.3 | ||||||||
Product Build | ||||||||||||
Summary | 0003931: expires in Hessian for rest-style responses | |||||||||||
Description |
(rep by Riccardo Cohen) To limit requests to resources that rarely change, sometimes in http responses, I simply add response.setDateHeader("Expires",now+600000); But in hessian, I have no access to the response object (only request object through ServiceContext.getContextRequest()) Is it possible ? |
|||||||||||
Steps To Reproduce | ||||||||||||
Additional Information | ||||||||||||
Attached Files | ||||||||||||
|
There are no notes attached to this issue. |
Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
26 total queries executed. 24 unique queries executed. |