[MGNLDIFF-30] Make the diff module configurable Created: 30/May/13  Updated: 23/Jul/13  Resolved: 04/Jun/13

Status: Closed
Project: Magnolia Diff Module
Component/s: None
Affects Version/s: None
Fix Version/s: 1.1.5

Type: Improvement Priority: Neutral
Reporter: Tomas Brimor Assignee: Jaroslav Simak
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File diffmoduleconfig.png    
Issue Links:
dependency
documentation
to be documented by DOCU-442 Diff module configuration Closed
duplicate
is duplicated by MGNLDIFF-29 Magnolia diff module to support custo... Closed
relation
is related to MGNLDIFF-32 Original host/port is used instead th... Closed
supersession
supersedes MGNLDIFF-29 Magnolia diff module to support custo... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Release notes required:
Yes
Date of First Response:

 Description   

It should be possible to configure the following for the diff module:

  • Host
    • Default value: user request host
  • Port
    • Deafult value: user request port
  • Headers
    • Default value: none
    • Should be possible to specify any number of headers to forward
  • Cookies
    • Default value: JSESSIONID
    • Should be possible to specify any number of cookies to forward

Suggested to to not allow specifying "Cookie" as a header to keep configuration of them separate. If "Cookie" is specified as a header an error message with directive to use 'Cookies' configuration should be logged.



 Comments   
Comment by Jan Haderka [ 04/Jun/13 ]

Looks good. Just one little thing - create config node under module on install otherwise ppl would have to do it manually and then it would not be observed until they restart the server.

Generated at Mon Feb 12 05:20:41 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.