adobe / helix-redirect Goto Github PK

currently it seems that an empty destination column seems to redirect to itself, instead the better behavior would probably be to consider the entry invalid and ignore it.

in order to use the content-proxy cache in fastly, the redirect json should be read via fastly.

Use the conditions-based redirects from helix-pages to create redirects in the outer CDN config when POSTing to this service with a tuple of (outer CDN) service ID and Fastly token.

All spreadsheets will be replicated to an edge dictionary for added performance. An operator can call this service after substantial redirect config changes.

Other config additions will still be effective, just slower as they are processed as part of the dispatch loop.

Requires adobe/helix-content-proxy#335 and adobe/helix-publish#800

see adobe/project-helix#508

• migrate code to use helix-deploy adapter
• update CI to use helix-deploy

This issue provides visibility into Renovate updates and their statuses. Learn more

Ignored or Blocked

These are blocked by an existing closed PR and will not be recreated unless you click a checkbox below.

• chore(deps): update dependency node-fetch to 2.6.7 [security]
• chore(deps): update dependency node-forge to 1.0.0 [security]
• chore(deps): update dependency path-parse to 1.0.7 [security]
• chore(deps): update dependency semver-regex to 3.1.3 [security]

• Check this box to trigger a request for Renovate to run again on this repository

there are a few usecases where query params are appended to a URL that are not actually evaluated on the server for example campaign ids in martech stacks. in that case it would be great to just pass on the query params and append those to the destination.

There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.

Error type: undefined. Note: this is a nested preset so please contact the preset author if you are unable to fix it yourself.

reading the redirect config should respect a potential x-github-token header.

it seems to be common that users have leading and trailing whitespaces in URLs in spreadsheet.
i believe it would be better to .trim() those.

Check out https://app.epsagon.com/spans/0e86a88f-5b38-a684-cd08-75360c75ce73?tab=timeline – no requests made within redirect can be seen. @tripodsan any idea if this is on us?