Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
ContentType not set when receiving message (3.0.8)
See original GitHub issueDescribe the bug
ContentType not set when receiving a message.
Which project is your bug related to?
- Client
To Reproduce
Steps to reproduce the behavior:
- Publish a
MqttApplicationMessagethat has itsContentTypeproperty set - Receive a
MqttApplicationMessageandContentTypeisnull
Expected behavior
Expected ContentType to be set to process the message body based on the ContentType.
Issue Analytics
- State:
- Created 4 years ago
- Comments:10 (3 by maintainers)
Top Results From Across the Web
ContentType not set when receiving message (3.0.8) #753
Describe the bug ContentType not set when receiving a message. Which project is your bug related to? Client To Reproduce Steps to reproduce ......
Read more >Content type not set while junit Spring MVC Controller?
In your case, what is happening is Spring is trying to figure out the view name and is getting the view name as...
Read more >RabbitListener (Spring AMQP 3.0.8 API)
This does not apply when the return type is Message or Message ; set the content type message property or header respectively, in...
Read more >F5 Access for iOS 3.0.8 - MyF5 | Support
Cannot import because the content type is not supported. This issue has been fixed, and now users can import a .pfx file certificate...
Read more >CRS Version 3.3.3 and 3.2.2 (covering several CVEs)
CVE-2022-39955 – Multiple charsets defined in Content-Type header. The OWASP ModSecurity Core Rule Set (CRS) is affected by a partial rule ...
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 Free
Top 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
The is now a pull request (#1527) which adds feature validations.
@chkr1011 I’m not using
WithProtocolVersion, I wasn’t aware there was an API for that. Based on the following docs it seems I was using the default value which isMqttProtocolVersion.V311.I’m using RabbitMQ MQTT plugin and that seems to be MQTT protocol version 3.1.1 which means I can’t make use of these properties.
What is the issue? I think this issue can be closed when linked to that issue.