@isa You are correct about this misleading redirect. Can you please create a new issue for this improvement?