Scala Stream Collector: can't parse all useragents?
See original GitHub issueNot sure where in the code it’s coming from, but I sometimes get the following warning:
05:23:09.567 [scala-stream-collector-akka.actor.default-dispatcher-12] WARN s.can.server.HttpServerConnection - Illegal request header: Illegal 'User-Agent' header: Invalid input '=', expected TokenChar, '/', OptWS, Comment, ProductVersionComment or EOI (line 1, pos 138):
Mozilla/5.0 (iPhone; CPU iPhone OS 6_0_1 like Mac OS X) AppleWebKit/536.26 (KHTML, like Gecko) Version/6.0 Mobile/10A523 Safari/8536.25 t=/eIf6uJm7bq+TQw7s39CJg==DMTVmSsvTYYvgFAgMkVQrp==
Issue Analytics
- State:
- Created 7 years ago
- Comments:8 (7 by maintainers)
Top Results From Across the Web
Collector Illegal Warning - AWS real-time pipeline - Discourse
Our team set up a Near-real-time snowplow using ec2 as a collector and point to the Kinesis. When we set up a real-time...
Read more >Parse out user agent the scala way in Play2 application
One way to do this is of course, as Sniffer suggested, do a partial match with unanchored like this:
Read more >Ignoring Unwanted Resources in APM - Datadog Docs
Configuring the Trace Agent to ignore certain spans or resources applies to all services that send traces to this particular Datadog Agent.
Read more >Configuration • Akka HTTP - Documentation
source client { # The default value of the `User-Agent` header to produce if ... a high value as all stream operations #...
Read more >Set up Fluent Bit as a DaemonSet to send logs to CloudWatch ...
Differences in log stream names — If you use the Fluent Bit optimized ... set FluentBitReadFromHead='On' and it will collect all logs in...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
it’s already in r92, the move to akka-http should solve it by itself since akka-http is more relaxed than spray as far as ua are concerned from looking at the code. I had an integration test planned for this.
A bit of an update on this: due to the parsing rules having been relaxed in akka-http less user-agents produce warnings.
However, despite the log messages, they are all successfully processed by the collector and further downstream.
Closing, thanks 👍 .