In the code I inherited there is a REST call that sets up user permissions for a virtual host in a rabbitmq installation. On my developer box I have latest RabbitMQ server installed, 3.7.7. The client software uses a Spring RestTemplate to query the host. It generates a PUT request to http://localhost:15672/api/permissions/myhost/administrator with a payload of
{"read":".*","write":".*","configure":".*"}
and an HTTP header Content-Type:application/json;charset=UTF-8
This all looks reasonable to me - but the response is
HTTP/1.1 415 Unsupported Media Type
This code is years old, and I suspect it is my RabbitMQ installation that is too new for it, but I'd like to rather make the code future-proof than to install an RabbitMQ from 2015 ...
I have googled extensively on this issue but all I found was some bug about doubled headers in the rabbitmq client software that is not in use here. I traced it into apache httpclient classes and there is nothing on the sender side that smells.
Any suggestions what is wrong?
--
You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-users+unsubscribe@googlegroups.com.
To post to this group, send email to rabbitmq-users@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
The suggestion is absolutely valid, although I would have to file a change request first, get approval to change the code, get it into sprint backlog. I need a solution that I can apply yesterday without to fight buerocratic trolls…
From: rabbitm...@googlegroups.com <rabbitm...@googlegroups.com>
On Behalf Of Michael Klishin
Sent: 15 September, 2018 3:47
To: rabbitm...@googlegroups.com
Subject: Re: [rabbitmq-users] 415 Unsupported Media Type issue
We had something similar in the early years of Hop [1] but I don't remember the specifics.
Just use Hop instead of reinventing it.
On Fri, Sep 14, 2018 at 4:25 AM, <kai.hac...@nzqa.govt.nz> wrote:
In the code I inherited there is a REST call that sets up user permissions for a virtual host in a rabbitmq installation. On my developer box I have latest RabbitMQ server installed, 3.7.7. The client software uses a Spring RestTemplate to query the host. It generates a PUT request to http://localhost:15672/api/permissions/myhost/administrator with a payload of
{"read":".*","write":".*","configure":".*"}and an HTTP header
Content-Type:application/json;charset=UTF-8This all looks reasonable to me - but the response is
HTTP/1.1 415 Unsupported Media TypeThis code is years old, and I suspect it is my RabbitMQ installation that is too new for it, but I'd like to rather make the code future-proof than to install an RabbitMQ from 2015 ...
I have googled extensively on this issue but all I found was some bug about doubled headers in the rabbitmq client software that is not in use here. I traced it into apache httpclient classes and there is nothing on the sender side that smells.
Any suggestions what is wrong?
--
You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-user...@googlegroups.com.
To post to this group, send email to rabbitm...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
MK
Staff Software Engineer, Pivotal/RabbitMQ
--
You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
rabbitmq-user...@googlegroups.com.
To post to this group, send email to
rabbitm...@googlegroups.com.
For more options, visit
https://groups.google.com/d/optout.
Tell us what you think.
NZQA would like your feedback on the service we provide so that we can improve the way we work with you.
Please use this link to complete our anonymous customer satisfaction survey.
********************************************************************************
This
email may contain legally privileged information and is intended only for the
addressee. It is not necessarily the official view or
communication of the
New Zealand Qualifications Authority. If you are not the intended recipient you
must not use, disclose, copy or distribute this email or
information in it.
If you have received this email in error, please contact the sender immediately.
NZQA does not accept any liability for changes made to this email or attachments
after sending by NZQA.
All emails have been scanned for viruses and content by MailMarshal.
NZQA
reserves the right to monitor all email communications through its network.
********************************************************************************
For curiosity reasons I checked the project out and this is what the API documentation says about the administrative requests:
Managing Users
TBD
Managing Permissions
TBD
This would not get me very far even if I would apply a migration below the radar… ☹
From: rabbitm...@googlegroups.com <rabbitm...@googlegroups.com>
On Behalf Of Michael Klishin
Sent: 15 September, 2018 3:47
To: rabbitm...@googlegroups.com
Subject: Re: [rabbitmq-users] 415 Unsupported Media Type issue
We had something similar in the early years of Hop [1] but I don't remember the specifics.
On Fri, Sep 14, 2018 at 4:25 AM, <kai.hac...@nzqa.govt.nz> wrote:
In the code I inherited there is a REST call that sets up user permissions for a virtual host in a rabbitmq installation. On my developer box I have latest RabbitMQ server installed, 3.7.7. The client software uses a Spring RestTemplate to query the host. It generates a PUT request to http://localhost:15672/api/permissions/myhost/administrator with a payload of
{"read":".*","write":".*","configure":".*"}and an HTTP header
Content-Type:application/json;charset=UTF-8This all looks reasonable to me - but the response is
HTTP/1.1 415 Unsupported Media TypeThis code is years old, and I suspect it is my RabbitMQ installation that is too new for it, but I'd like to rather make the code future-proof than to install an RabbitMQ from 2015 ...
I have googled extensively on this issue but all I found was some bug about doubled headers in the rabbitmq client software that is not in use here. I traced it into apache httpclient classes and there is nothing on the sender side that smells.
Any suggestions what is wrong?
--
You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-user...@googlegroups.com.
To post to this group, send email to rabbitm...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
MK
Staff Software Engineer, Pivotal/RabbitMQ
--
You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
rabbitmq-user...@googlegroups.com.
To post to this group, send email to
rabbitm...@googlegroups.com.
For more options, visit
https://groups.google.com/d/optout.
Tell us what you think.
The suggestion is absolutely valid, although I would have to file a change request first, get approval to change the code, get it into sprint backlog. I need a solution that I can apply yesterday without to fight buerocratic trolls…
From: rabbitmq-users@googlegroups.com <rabbitmq-users@googlegroups.com> On Behalf Of Michael Klishin
Sent: 15 September, 2018 3:47
To: rabbitmq-users@googlegroups.com
Subject: Re: [rabbitmq-users] 415 Unsupported Media Type issue
We had something similar in the early years of Hop [1] but I don't remember the specifics.
Just use Hop instead of reinventing it.
On Fri, Sep 14, 2018 at 4:25 AM, <kai.hac...@nzqa.govt.nz> wrote:
In the code I inherited there is a REST call that sets up user permissions for a virtual host in a rabbitmq installation. On my developer box I have latest RabbitMQ server installed, 3.7.7. The client software uses a Spring RestTemplate to query the host. It generates a PUT request to http://localhost:15672/api/permissions/myhost/administrator with a payload of
{"read":".*","write":".*","configure":".*"}and an HTTP header
Content-Type:application/json;charset=UTF-8This all looks reasonable to me - but the response is
HTTP/1.1 415 Unsupported Media TypeThis code is years old, and I suspect it is my RabbitMQ installation that is too new for it, but I'd like to rather make the code future-proof than to install an RabbitMQ from 2015 ...
I have googled extensively on this issue but all I found was some bug about doubled headers in the rabbitmq client software that is not in use here. I traced it into apache httpclient classes and there is nothing on the sender side that smells.
Any suggestions what is wrong?
--
You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-users+unsubscribe@googlegroups.com.
To post to this group, send email to rabbitmq-users@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--MK
Staff Software Engineer, Pivotal/RabbitMQ
--
You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-users+unsubscribe@googlegroups.com.
To post to this group, send email to rabbitmq-users@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Tell us what you think.
NZQA would like your feedback on the service we provide so that we can improve the way we work with you.
Please use this link to complete our anonymous customer satisfaction survey.
********************************************************************************
This email may contain legally privileged information and is intended only for the addressee. It is not necessarily the official view or
communication of the New Zealand Qualifications Authority. If you are not the intended recipient you must not use, disclose, copy or distribute this email or
information in it. If you have received this email in error, please contact the sender immediately. NZQA does not accept any liability for changes made to this email or attachments after sending by NZQA.All emails have been scanned for viruses and content by MailMarshal.
NZQA reserves the right to monitor all email communications through its network.********************************************************************************
--
You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-users+unsubscribe@googlegroups.com.
To post to this group, send email to rabbitmq-users@googlegroups.com.
HttpHeaders headers = new HttpHeaders();
headers.setContentType(MediaType.APPLICATION_JSON);
HttpEntity<String> entity = new HttpEntity<String>(requestJson, headers);
ResponseEntity<String> response = restTemplate.put(url, entity);--
You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-users+unsubscribe@googlegroups.com.
To post to this group, send email to rabbitmq-users@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-user...@googlegroups.com.
To post to this group, send email to rabbitm...@googlegroups.com.