Skip to content

Allow setting the HTTP Origin header - #44

Open
Riabkov wants to merge 3 commits into
Optable:masterfrom
postindustria-tech:feature/allow-setting-origin-header
Open

Allow setting the HTTP Origin header#44
Riabkov wants to merge 3 commits into
Optable:masterfrom
postindustria-tech:feature/allow-setting-origin-header

Conversation

@Riabkov

@Riabkov Riabkov commented Jul 27, 2026

Copy link
Copy Markdown
  • Add OptableConfig.origin
  • Append 'Origin' header in RequestInterceptor.kt if config.origin is not null or empty
  • Added 'Origin' header tests to MockWebServerTest for green/empty/null config.origin
  • Add origin to Kotlin and Java demo apps' Applications
  • Update README.md

Closes #41

- Append 'Origin' header in RequestInterceptor.kt if config.origin is not null or empty
- Added 'Origin' header tests to MockWebServerTest for green/empty/null config.origin
- Add origin to Kotlin and Java demo apps' Applications
- Update README.md
@Riabkov
Riabkov force-pushed the feature/allow-setting-origin-header branch from cbe807c to 683a547 Compare July 27, 2026 12:01
Java callers could only reach the origin parameter through the full
11-argument constructor, which forced the Java demo to restate every
default. A public var matches consents, and matches the iOS SDK where
origin is a settable property.
The blank case covered whitespace only, so the empty string the PR
description claims to cover went untested.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Allow setting the HTTP Origin header

2 participants