[MAGNOLIA-645] Make Configuration URL consistent Created: 18/Feb/06 Updated: 20/Feb/15 Resolved: 12/Mar/06 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | core |
| Affects Version/s: | 2.1.4 |
| Fix Version/s: | 3.0 Beta 1 |
| Type: | Improvement | Priority: | Minor |
| Reporter: | Giancarlo Berner | Assignee: | Fabrizio Giustina |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Windows XP |
||
| 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)
|
| Date of First Response: |
| Description |
|
Some Configuration settings require a URL. But it's never clear, if the URL has to be added with or without the underlying protocol. Especially with the domain in the caching settings we noticed that often the protocol is left away and obviousl Magnolia cache will not be working. Thanks |
| Comments |
| Comment by Fabrizio Giustina [ 12/Mar/06 ] |
|
fixed in trunk, now everything is consistent: Config/server/cache/domain has been totally removed due to the cache refactoring, no need to worry about it Subscriber now support a "URL" property (instead of address) where you need a full url with protocol, just like for senderURL. Configuration with address/domain still works, with a deprecation warning written to the log. |