Thank you for sharing this use case!! I presume you have had users complain about case sensitivity and that have been confused by trying to reach content?
We will definitely share this feedback with developers! One "option" that you can use today (although it is admittedly a bit of a hack):
- Create a static
HTML page with the following HTML in it:
<head><meta http-equiv='refresh' content='0; URL=/mycontent'></head>
- Deploy this static HTML page to Connect and give it the vanity URL
/MyContent
- When users visit this page, their browser will automatically be redirected to your desired location
I started thinking about this, and another approach you could take is define a single Rmd that does this for you (and is configurable by an environment variable). Then you just deploy this to your Connect server many times as a redirector wherever you need it!
Granted, you end up with a whole bunch of random, useless content, but it gives you the behavior you want in the short term!
Plus, you could tag them all the same to easily find / remove if and when we have this as a more supported feature within Connect!
Because I found this intriguing, I made a trivial little example... I also created a manifest.json so you can easily deploy with git-backed deployment too 