diff options
| author | Simon MacMullen <simon@rabbitmq.com> | 2012-01-25 15:17:48 +0000 |
|---|---|---|
| committer | Simon MacMullen <simon@rabbitmq.com> | 2012-01-25 15:17:48 +0000 |
| commit | 77c52e656733bee097a274a050bb0029cc4c2915 (patch) | |
| tree | ae27e61c8dff00c144efea2d931113289b8e8107 | |
| parent | ae8815c85d3c4cf9caa98c4f8a08f59629f23ea3 (diff) | |
| download | rabbitmq-server-77c52e656733bee097a274a050bb0029cc4c2915.tar.gz | |
I think this should be a soft error. Although the spec does say to use command-invalid when the client attempts to declare an exchange of an unknown type, that's much more obviously the client's fault. So let's go with an old favourite.
| -rw-r--r-- | src/rabbit_exchange_type_invalid.erl | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/rabbit_exchange_type_invalid.erl b/src/rabbit_exchange_type_invalid.erl index fc589450..8f60f7d8 100644 --- a/src/rabbit_exchange_type_invalid.erl +++ b/src/rabbit_exchange_type_invalid.erl @@ -34,7 +34,7 @@ serialise_events() -> false. route(#exchange{name = Name, type = Type}, _) -> rabbit_misc:protocol_error( - command_invalid, + precondition_failed, "Cannot route message through ~s: exchange type ~s not found", [rabbit_misc:rs(Name), Type]). |