[SEO-32] Consolidate / simplify fetcher configuration Created: 29/Oct/20 Updated: 29/Oct/20 |
|
| Status: | Open |
| Project: | Search Engine Optimization |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Andrew Warinner | Assignee: | Andrew Warinner |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| 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)
|
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
| Description |
|
Auditors that use a fetcher to retrieve a rendered page each have an individually configured fetcher. There are many auditors using fetchers in the default bootstrapped configuration. The configured HTTP fetchers probably won't work out of the box after installation: they assume Magnolia is running at http://localhost:8080 in the root context. Many HTTP fetcher configuration may have to be changed. The HTTP fetcher configuration allows retrieval with personas to test personalization scenarios. Possibilities to consider:
|