Skip to content
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

Support Rest sensor XML responses that don't have an XML content type set #117715

Open
wants to merge 3 commits into
base: dev
Choose a base branch
from

Conversation

khcnz
Copy link

@khcnz khcnz commented May 19, 2024

Proposed change

Currently the rest sensor parses the returned result content as xml rather than json when the content-type is 'correctly' set by a server to include one of a set of specified xml mime types (such as text/xml).

This change extends this matching logic to also also look so see if the file extension ends in xml, or if the content starts with <?xml version="1.0" in order to support less compliant servers that are returning xml results without setting a 'correct' mime type (which I have come across).

It's unlikely this would be a breaking change for anyone as the current code falls back to parsing as json if an xml conversion fails.

Type of change

  • Dependency upgrade
  • Bugfix (non-breaking change which fixes an issue)
  • New integration (thank you!)
  • New feature (which adds functionality to an existing integration)
  • Deprecation (breaking change to happen in the future)
  • Breaking change (fix/feature causing existing functionality to break)
  • Code quality improvements to existing code or addition of tests

Additional information

Checklist

  • The code change is tested and works locally.
  • Local tests pass. Your PR cannot be merged unless tests pass
  • There is no commented out code in this PR.
  • I have followed the development checklist
  • I have followed the perfect PR recommendations
  • The code has been formatted using Ruff (ruff format homeassistant tests)
  • Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

If the code communicates with devices, web services, or third-party tools:

  • The manifest file has all fields filled out correctly.
    Updated and included derived files by running: python3 -m script.hassfest.
  • New or updated dependencies have been added to requirements_all.txt.
    Updated by running python3 -m script.gen_requirements_all.
  • For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
  • Untested files have been added to .coveragerc.

To help with the load of incoming pull requests:

Copy link

@home-assistant home-assistant bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @khcnz

It seems you haven't yet signed a CLA. Please do so here.

Once you do that we will be able to review and accept this pull request.

Thanks!

@home-assistant
Copy link

Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍

Learn more about our pull request process.

@khcnz khcnz marked this pull request as ready for review May 19, 2024 05:28
@MartinHjelmare MartinHjelmare changed the title Extend Rest Sensor support for XML responses that don't have an XML content type set Support Rest sensor XML responses that don't have an XML content type set May 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant