Protocol support for batching?
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- typescript
- Domain
- api
Research direction
Start at the AnalyticsBrowser.load entry point and trace how the Segment.io integration handles the protocol and deliveryStrategy batching options. Reproduce the configuration with batching enabled and verify that batched requests honor protocol: "http" rather than using HTTPS.
Written by the indexing model from the issue text.
Description
Hello! We have a backend that's processing batches of events. While I was doing some debugging locally, I noticed that if the delivery strategy is set to batching, specifying the protocol as 'http' doesn't have any effect, and the calls are still sent through HTTPS.
Once I disabled batching, specifying the protocol as 'http' started working.
AnalyticsBrowser.load(
{
writeKey: 'VALUE_NOT_REQUIRED',
cdnURL: baseUrl,
cdnSettings: { integrations: {['Segment.io']: {}}},
},
{
integrations: {
'Segment.io': {
apiHost: baseUrl,
protocol: "http",
deliveryStrategy: {
strategy: "batching",
config: {
size: 10,
timeout: 5000
}
},
addBundledMetadata: false
}
}
}
);
Is this by design or can something be done here to allow batches to go through http?
- Dominant language
- TypeScript
- Stars
- 477
- Forks
- 160
- Avg merge
- 6h 19m
- Merged PRs (30d)
- 4
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from segmentio/analytics-next
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
segmentio/analytics-next#1324 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
segmentio/analytics-next#1366 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
segmentio/analytics-next#1338 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
segmentio/analytics-next#1337 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
segmentio/analytics-next#1332 ·
All issues in segmentio/analytics-next
Similar issues
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 76/100
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
vercel/react-tweet#225 ·