Skip to content

Commit 6d19d4f

Browse files
committed
Fix links
Now that RabbitMQ 4.0 docs are released omit the `next` in the URL.
1 parent 1cf60c6 commit 6d19d4f

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

blog/2024-08-05-native-amqp/index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -213,7 +213,7 @@ This extensive effort was due to several factors:
213213
* **Rolling Upgrades:** We support rolling upgrades from RabbitMQ 3.13 to 4.0, allowing you to upgrade your AMQP 1.0 workloads without downtime.
214214

215215
Even though RabbitMQ 4.0 supports AMQP 1.0 natively, this does not imply that RabbitMQ supports all AMQP 1.0 features.
216-
Like any other AMQP 1.0 broker, RabbitMQ's AMQP 1.0 implementation has [documented limitations](/docs/next/amqp#limitations).
216+
Like any other AMQP 1.0 broker, RabbitMQ's AMQP 1.0 implementation has [documented limitations](/docs/amqp#limitations).
217217

218218
## RabbitMQ AMQP 1.0 clients
219219

blog/2024-08-21-amqp-benchmarks/index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -160,7 +160,7 @@ Time [s] Count [m] Rate [m/s] CPU [%] RSS [M] Time [s] Count [m]
160160
For our AMQP 0.9.1 benchmarks we use [PerfTest](https://perftest.rabbitmq.com/).
161161
We try to run a somewhat fair comparison of our previous AMQP 1.0 benchmark.
162162

163-
Since an AMQP 1.0 [/queues/:queue](/docs/next/amqp#target-address-v2) target address sends to the default exchange, we also send to the default exchange via AMQP 0.9.1.
163+
Since an AMQP 1.0 [/queues/:queue](/docs/amqp#target-address-v2) target address sends to the default exchange, we also send to the default exchange via AMQP 0.9.1.
164164
Since we used [durable](https://docs.oasis-open.org/amqp/core/v1.0/os/amqp-core-messaging-v1.0-os.html#type-header) messages with AMQP 1.0, we set the `persistent` flag in AMQP 0.9.1.
165165
Since RabbitMQ settles with the [released](https://docs.oasis-open.org/amqp/core/v1.0/os/amqp-core-messaging-v1.0-os.html#type-released) outcome when a message cannot be routed, we set the `mandatory` flag in AMQP 0.9.1.
166166
Since RabbitMQ `v4.0.0-beta.5` uses a default `rabbit.max_link_credit` of 128 granting 128 more credits to the sending client when remaining credit falls below 0.5 * 128, we configure the AMQP 0.9.1 publisher to have at most 1.5 * 128 = 192 messages unconfirmed at a time.

0 commit comments

Comments
 (0)