-
Notifications
You must be signed in to change notification settings - Fork 467
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Send Version of CLI along with Header #28594
Comments
nollymar
moved this from Next 1-3 Sprints
to Current Sprint Backlog
in dotCMS - Product Planning
May 29, 2024
fabrizzio-dotCMS
moved this from Current Sprint Backlog
to In Progress
in dotCMS - Product Planning
Jun 10, 2024
Merged
github-project-automation
bot
moved this from In Review
to Internal QA
in dotCMS - Product Planning
Jun 13, 2024
github-project-automation
bot
moved this from Internal QA
to Current Sprint Backlog
in dotCMS - Product Planning
Jun 14, 2024
nollymar
moved this from Current Sprint Backlog
to Internal QA
in dotCMS - Product Planning
Jun 14, 2024
Bug introduced in Native build. #28915 |
github-project-automation
bot
moved this from QA - Backlog
to Internal QA
in dotCMS - Product Planning
Jun 25, 2024
you can set a proxy in front of dotCMS to intercept all apis call using Charles for example |
Fixed, tested on trunk // latest CLI version |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Parent Issue
#28378
Task
We want to send the version of the CLI along with the Headers when making a call to an instance of dotCMS.
At some point in the future, we'll want the dotCMS instance to be able to look at the headers and respond, "You're using an out of date version of the CLI, time up upgrade!"
But right now, we just want to include the version in the headers so that we won't get into a spot where we can't add that response improvement to dotCMS in the future.
Proposed Objective
Same as Parent Issue
Proposed Priority
Same as Parent Issue
Acceptance Criteria
No response
External Links... Slack Conversations, Support Tickets, Figma Designs, etc.
No response
Assumptions & Initiation Needs
No response
Quality Assurance Notes & Workarounds
No response
Sub-Tasks & Estimates
No response
The text was updated successfully, but these errors were encountered: