Unable to have # character in Path for RedirectConfig
When attempting to add a redirect to my ALB listener rule, having a # character in the Path attribute causes it to view the path as invalid.
This is true both on the console and cloudformation. Is this a bug or intended functionality?
Unfortunately, this is the same behavior when using the console. If you try from there, it returns
Invalid path message and doesn't let you save the rule.
Traditionally, 3xx redirects don't allow this generally, since the anchor is only processed on the client side. More recently, that spec has been updated, however ALB still doesn't support it properly.
That said, I was experimenting with this a bit, and I found that it seems to work if you put this into the query attribute. It does add a ? character as well, but the anchor seems to work. For example:
This rule causes a redirect to
https://en.wikipedia.org:443/wiki/Foobar?#See_also, which does seem to behave as an anchor link should, though the
? should generally be unneeded for this.
Using Cloudfront Function for redirect of specific pathasked a year ago
Unable to have # character in Path for RedirectConfigasked 25 days ago
Root Path Patternasked 3 years ago
unable to use table_import_from_s3 with any pathasked 2 years ago
How to validate request path parameters for API Gateway in OpenAPI definitionasked 5 months ago
Delete base path mapping in API Gateway doesn't workasked 5 years ago
Network path between ALB and ECS Fargate taskAccepted Answerasked 5 months ago
Blob values must be a path to a fileasked 5 years ago
Informatica to AWS Glue Migration PathAccepted Answerasked 3 years ago
ALB Rewrite-path and alterasked 5 months ago