Ticket #336 (closed Defect: fixed)
WAR deployment issues
| Reported by: | jri | Owned by: | jri |
|---|---|---|---|
| Priority: | Major | Milestone: | Release 4.1 |
| Component: | DeepaMehta Standard Distribution | Version: | 4.0.12 |
| Keywords: | Cc: | dgf, Malte | |
| Complexity: | 5 | Area: | |
| Module: |
Description
1) Content Negotiation doesn't work (Topicmaps plugin)
2) Bad Requests (Files plugin)
3) File access security check fails (Files plugin)
Change History
comment:2 Changed 12 years ago by Jörg Richter
Files plugin: fix bad requests (#336).
Slashes within file paths contained in the request URI are not encoded anymore (%2F).
Issues 1) and 2) of the original description should be fixed now. 3) is pending.
See ticket 336.
comment:3 Changed 12 years ago by Jörg Richter
Files plugin: relative filerepo path (#336).
For the dm4.filerepo.path config property a relative path can be specified.
(Absolute paths are still supported.)
Not yet merged into master.
To be discussed.
See ticket 336.
comment:4 Changed 12 years ago by Jörg Richter
RESTClient: fix content negotiation (#336).
The RESTClient sends the proper Accept headers.
Display of text files works again (was broken with previous commit).
RESTClient API:
The dm4c.restc.request() method has an optional 5th parameter: "response_data_type"
It affects the "Accept" header to be sent and controls the post-processing of the response data.
2 possible values:
"json" - the response data is parsed into a JavaScript? object. The default.
"text" - the response data is returned as is.
See ticket 336.
RESTClient: fix content negotiation (#336).
The RESTClient sends the proper Accept headers.
Display of text files works again (was broken with previous commit).
RESTClient API:
The dm4c.restc.request() method has an optional 5th parameter: "response_data_type"
It affects the "Accept" header to be sent and controls the post-processing of the response data.
2 possible values:
See ticket 336.