I am seeing the same behavior. Has anyone else resolved this issue?
Setting the referer field is something the browser does, CQ can't force the browser to set the referer field if it isn't being set. Generally how browsers deal with this though is to ignore the 301 redirect in the referer chain. So for example:
- User is on a google search results page. They click on a link that doesn't redirect - google is referer.
- User is on a google search results page. They click on a link that does a 301 redirect - google is still the referer - not the 301 URL.
- User enters a URL in their browser > 301 redirect > no referer because it is direct traffic as far as the browser is concerned.
I don't think there is an out of the box way to acheive your goal.