Server has always used Authorization header.
We did not change anything on our side in the last few day did you make an upgrade of your agent ? If yes there is something that did change on that part.
What is that GET /dashboard/support ? A smart chart ? Could you give a more context please
this could have been a change months ago and we didn’t notice until now
we have a custom page running on the backend server we wanted to limit users already logged into Forest. I’m pretty sure it used to use cookies and this worked because we used it before
Please consider the fix of enlarging the cookies scope as temporary, not reliable.
It’s a security lack, and you will need to support it by yourself, something we can do for you.
If it’s possible, can you please express what is the business case you considered better to solve with custom pages instead of using the Forest features? It can also help us improve the product.
Oh yes I understand that, thank you.
This is a technical description, right?
If you agree to share the information with us, can you explain the business need this?
What is the business purpose of these custom pages? What is the functionnal service covered by these custom pages?
I insist because, Forest UI can address almost everything. I think at 99% that I will be able to provide you a way of doing the same feature in an integrated way, so you won’t have to care about security, updates and so on.
And more: you will benefit from features that are supported and used (tested) by a whole community.