Maintenance – Change header x on behalf of

[derpixler]

What

Replaces the deprecated X-On-Behalf-Of HTTP header with From as required by Zammad >= 6.5.

Why

In Zammad 6.5, using X-On-Behalf-Of causes a 500 Internal Server Error because the
deprecation warning itself crashes. Zammad now expects the standard From header.
The documentation has already been updated (zammad/zammad-documentation#626).

Closes #64.

Changes

• src/Client.php — Header renamed from X-On-Behalf-Of to From
• README.md — Documentation updated to reference the From header
• CHANGELOG.md — Entry added

Tests

• test/ZammadAPIClient/ClientTest.php — 3 new mock-based unit tests covering:

  • From header is set when setOnBehalfOfUser() is called
  • From header is absent by default
  • From header is removed after unsetOnBehalfOfUser()
  • 1 integration test (testFromHeaderAgainstZammad) that verifies the header works against a real Zammad instance (skipped when env vars are not configured)

• test/ZammadAPIClient/EnvConfigTrait.php — New trait providing getZammadConfig() and createZammadClient() to deduplicate environment-variable handling between AbstractBaseTest and ClientTest

• test/ZammadAPIClient/Resource/AbstractBaseTest.php — Refactored to use EnvConfigTrait instead of inline env-var logic

Backward Compatibility

• Method names setOnBehalfOfUser() and unsetOnBehalfOfUser() remain unchanged
• From header is supported by Zammad pre-6.5 as well