root
/
rabbitmq-server
mirror of https://github.com/rabbitmq/rabbitmq-server.git
1
0
Fork 0
Code Issues Actions Packages Projects Releases Wiki Activity
rabbitmq-server/deps/rabbitmq_web_stomp/test/unit_SUITE.erl

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

57 lines
1.9 KiB
Erlang
Raw Permalink Normal View History

Switch to MPL2
2020-07-15 08:19:24 +08:00
%% This Source Code Form is subject to the terms of the Mozilla Public
%% License, v. 2.0. If a copy of the MPL was not distributed with this
%% file, You can obtain one at https://mozilla.org/MPL/2.0/.
Support typical RabbitMQ TCP socket options The port option in the tcp_options entry takes now precedence explicitly over the port option at the root of the env proplist. It was previously the case, even if the opposite was advertized: there would be 2 port entries in the Ranch options and Ranch would take the one from tcp_options. It's now possible to use strings for IP addresses, not only tuples. The correct binding address and port are now used in the log message. Fixes #69
2017-03-10 20:35:09 +08:00
%%
(c) year bumps
2024-01-02 11:02:20 +08:00
%% Copyright (c) 2007-2025 Broadcom. All Rights Reserved. The term “Broadcom” refers to Broadcom Inc. and/or its subsidiaries. All rights reserved.
Support typical RabbitMQ TCP socket options The port option in the tcp_options entry takes now precedence explicitly over the port option at the root of the env proplist. It was previously the case, even if the opposite was advertized: there would be 2 port entries in the Ranch options and Ranch would take the one from tcp_options. It's now possible to use strings for IP addresses, not only tuples. The correct binding address and port are now used in the log message. Fixes #69
2017-03-10 20:35:09 +08:00
%%
-module(unit_SUITE).
-compile(export_all).
all() ->
[
get_tcp_conf,
get_tcp_port,
get_binding_address
].
%% -------------------------------------------------------------------
%% Testsuite setup/teardown.
%% -------------------------------------------------------------------
init_per_group(_, Config) ->
Config.
end_per_group(_, Config) ->
Config.
%% -------------------------------------------------------------------
%% Testcases.
%% -------------------------------------------------------------------
get_tcp_conf(_Config) ->
Configure Ranch to use max_connections value of 'infinity' by default Also make the value configurable via web_stomp.max_connections. While at it, reduce module naming delta with the Web MQTT plugin. We mean to do this every time we have to touch this codebase, so let's finally do the renaming. Closes #113. References rabbitmq/rabbitmq-web-mqtt#28, rabbitmq/rabbitmq-web-mqtt#55.
2019-06-07 18:10:03 +08:00
[{ip, {127, 0, 0, 1}}, {port, 15674}] = lists:sort(rabbit_web_stomp_listener:get_tcp_conf(
Support typical RabbitMQ TCP socket options The port option in the tcp_options entry takes now precedence explicitly over the port option at the root of the env proplist. It was previously the case, even if the opposite was advertized: there would be 2 port entries in the Ranch options and Ranch would take the one from tcp_options. It's now possible to use strings for IP addresses, not only tuples. The correct binding address and port are now used in the log message. Fixes #69
2017-03-10 20:35:09 +08:00
[{ip, {127, 0, 0, 1}}, {port, 1245}], 15674
)),
Configure Ranch to use max_connections value of 'infinity' by default Also make the value configurable via web_stomp.max_connections. While at it, reduce module naming delta with the Web MQTT plugin. We mean to do this every time we have to touch this codebase, so let's finally do the renaming. Closes #113. References rabbitmq/rabbitmq-web-mqtt#28, rabbitmq/rabbitmq-web-mqtt#55.
2019-06-07 18:10:03 +08:00
[{ip, {127, 0, 0, 1}}, {port, 15674}] = lists:sort(rabbit_web_stomp_listener:get_tcp_conf(
Support typical RabbitMQ TCP socket options The port option in the tcp_options entry takes now precedence explicitly over the port option at the root of the env proplist. It was previously the case, even if the opposite was advertized: there would be 2 port entries in the Ranch options and Ranch would take the one from tcp_options. It's now possible to use strings for IP addresses, not only tuples. The correct binding address and port are now used in the log message. Fixes #69
2017-03-10 20:35:09 +08:00
[{ip, {127, 0, 0, 1}}], 15674
)),
Configure Ranch to use max_connections value of 'infinity' by default Also make the value configurable via web_stomp.max_connections. While at it, reduce module naming delta with the Web MQTT plugin. We mean to do this every time we have to touch this codebase, so let's finally do the renaming. Closes #113. References rabbitmq/rabbitmq-web-mqtt#28, rabbitmq/rabbitmq-web-mqtt#55.
2019-06-07 18:10:03 +08:00
[{port, 15674}] = lists:sort(rabbit_web_stomp_listener:get_tcp_conf(
Support typical RabbitMQ TCP socket options The port option in the tcp_options entry takes now precedence explicitly over the port option at the root of the env proplist. It was previously the case, even if the opposite was advertized: there would be 2 port entries in the Ranch options and Ranch would take the one from tcp_options. It's now possible to use strings for IP addresses, not only tuples. The correct binding address and port are now used in the log message. Fixes #69
2017-03-10 20:35:09 +08:00
[], 15674
)),
ok.
get_tcp_port(_Config) ->
Configure Ranch to use max_connections value of 'infinity' by default Also make the value configurable via web_stomp.max_connections. While at it, reduce module naming delta with the Web MQTT plugin. We mean to do this every time we have to touch this codebase, so let's finally do the renaming. Closes #113. References rabbitmq/rabbitmq-web-mqtt#28, rabbitmq/rabbitmq-web-mqtt#55.
2019-06-07 18:10:03 +08:00
15674 = rabbit_web_stomp_listener:get_tcp_port([{port, 15674}]),
15674 = rabbit_web_stomp_listener:get_tcp_port([{port, 15674}, {tcp_config, []}]),
12345 = rabbit_web_stomp_listener:get_tcp_port([{port, 15674}, {tcp_config, [{port, 12345}]}]),
Support typical RabbitMQ TCP socket options The port option in the tcp_options entry takes now precedence explicitly over the port option at the root of the env proplist. It was previously the case, even if the opposite was advertized: there would be 2 port entries in the Ranch options and Ranch would take the one from tcp_options. It's now possible to use strings for IP addresses, not only tuples. The correct binding address and port are now used in the log message. Fixes #69
2017-03-10 20:35:09 +08:00
ok.
get_binding_address(_Config) ->
Configure Ranch to use max_connections value of 'infinity' by default Also make the value configurable via web_stomp.max_connections. While at it, reduce module naming delta with the Web MQTT plugin. We mean to do this every time we have to touch this codebase, so let's finally do the renaming. Closes #113. References rabbitmq/rabbitmq-web-mqtt#28, rabbitmq/rabbitmq-web-mqtt#55.
2019-06-07 18:10:03 +08:00
"0.0.0.0" = rabbit_web_stomp_listener:get_binding_address([]),
"192.168.1.10" = rabbit_web_stomp_listener:get_binding_address([{ip, "192.168.1.10"}]),
"192.168.1.10" = rabbit_web_stomp_listener:get_binding_address([{ip, {192, 168, 1, 10}}]),
Support typical RabbitMQ TCP socket options The port option in the tcp_options entry takes now precedence explicitly over the port option at the root of the env proplist. It was previously the case, even if the opposite was advertized: there would be 2 port entries in the Ranch options and Ranch would take the one from tcp_options. It's now possible to use strings for IP addresses, not only tuples. The correct binding address and port are now used in the log message. Fixes #69
2017-03-10 20:35:09 +08:00
ok.