Skip to content
This repository has been archived by the owner on May 3, 2021. It is now read-only.

Base64 Encoding Bug #82

Closed
sgammon opened this issue Apr 20, 2018 · 0 comments · Fixed by #83
Closed

Base64 Encoding Bug #82

sgammon opened this issue Apr 20, 2018 · 0 comments · Fixed by #83
Assignees
@sgammon
Labels
bug telemetry

Comments

@sgammon
Copy link
Contributor

sgammon commented Apr 20, 2018

There is an issue in some browsers (strange ones) where an extra = is appended to the URL for the telemetry collection name of a given generic event. This breaks parsing of the URL endpoint by ESP and results in a 400 or 500 series error, depending on the browser and failure.

So far, the behavior has been observed in:

  • Googlebot
  • Chrome 65 (wtf)
  • Mozilla
  • Edge 16
@sgammon sgammon self-assigned this Apr 20, 2018
sgammon pushed a commit that referenced this issue Apr 20, 2018
Bugfix: Base64 Encoding
1ffc401 
Fix a small, sneaky base64 encoding bug in some browsers that don't
handle regexes well. Fixes and closes #82.

- [x] Fix regex bug
- [x] Bump version -> `1.0.6`
@sgammon sgammon mentioned this issue Apr 20, 2018
Merged
2 tasks
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@sgammon sgammon

Labels
bug telemetry
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Bugfix: Base64 Encoding Bloombox/JS
1 participant
@sgammon