update fleetd-chrome to set expected HTTP headers (#31768)
# Checklist for submitter If some of the following don't apply, delete the relevant line. - [X] Changes file added for user-visible changes in `changes/`, `orbit/changes/` or `ee/fleetd-chrome/changes`. See [Changes files](https://github.com/fleetdm/fleet/blob/main/docs/Contributing/guides/committing-changes.md#changes-files) for more information. ## Testing - [ ] Added/updated automated tests - [ ] Where appropriate, [automated tests simulate multiple hosts and test for host isolation](https://github.com/fleetdm/fleet/blob/main/docs/Contributing/reference/patterns-backend.md#unit-testing) (updates to one hosts's records do not affect another) - [X] QA'd all new/changed functionality manually ## fleetd/orbit/Fleet Desktop - [X] Verified compatibility with the latest released version of Fleet (see [Must rule](https://github.com/fleetdm/fleet/blob/main/docs/Contributing/workflows/fleetd-development-and-release-strategy.md))
This commit is contained in:
@@ -1,3 +1,7 @@
|
||||
## fleetd-chrome 1.3.2 (August 8, 2025)
|
||||
|
||||
* Fixed a bug which caused fleetd-chrome to fail enrollment.
|
||||
|
||||
## fleetd-chrome 1.3.1 (May 20, 2024)
|
||||
|
||||
* Fixed bug where fleetd-chrome sent multiple read requests to Fleet server at the same time.
|
||||
|
||||
@@ -28,6 +28,10 @@ const request = async ({ path, body = {} }: requestArgs): Promise<any> => {
|
||||
|
||||
const options = {
|
||||
method: "POST",
|
||||
headers: {
|
||||
"Content-Type": "application/json",
|
||||
"Accept": "application/json",
|
||||
},
|
||||
body: JSON.stringify(body),
|
||||
};
|
||||
console.debug("Request:", target, options);
|
||||
|
||||
Reference in New Issue
Block a user