From c5814ff44d90a5215531c33ef1243483541cd32d Mon Sep 17 00:00:00 2001 From: msm1992 Date: Wed, 30 Oct 2024 12:27:53 +0530 Subject: [PATCH] Fix broken links --- en/docs/includes/design/invoke-prerelease-api.md | 6 +++--- .../customizing-api-template-for-gateway.md | 6 +++--- 2 files changed, 6 insertions(+), 6 deletions(-) diff --git a/en/docs/includes/design/invoke-prerelease-api.md b/en/docs/includes/design/invoke-prerelease-api.md index 91b8edbcb2..684480dbf8 100644 --- a/en/docs/includes/design/invoke-prerelease-api.md +++ b/en/docs/includes/design/invoke-prerelease-api.md @@ -1,16 +1,16 @@ ## Step 3 - Deploy the API -[Deploy the API](../../../../deploy-and-publish/deploy-on-gateway/deploy-api/deploy-an-api/) in order to make the API available in the respective Gateway. +[Deploy the API](../../../deploy-and-publish/deploy-on-gateway/deploy-api/deploy-an-api/) in order to make the API available in the respective Gateway. ## Step 4 - Test the API via the Publisher -Once deployed to the Gateway, you can [test the REST type APIs via the Publisher Portal](../../../../../design/create-api/create-rest-api/test-a-rest-api/). +Once deployed to the Gateway, you can [test the REST type APIs via the Publisher Portal](../../../design/create-api/create-rest-api/test-a-rest-api/). ## Step 5 - Publish the API as a Prototype !!! important - By default, from WSO2 API Manager 4.1.0 onwards, security is enabled for all the resources of the Prototype API. As a result, you need a subscription to invoke the API. - - Skip this step if you have [disabled security](../../../../design/api-security/api-authentication/disable-security/) for all the resources in the API. + - Skip this step if you have [disabled security](../../../design/api-security/api-authentication/disable-security/) for all the resources in the API. Follow the instructions below to attach Business Plans to the API. diff --git a/en/docs/reference/customize-product/extending-api-manager/extending-gateway/customizing-api-template-for-gateway.md b/en/docs/reference/customize-product/extending-api-manager/extending-gateway/customizing-api-template-for-gateway.md index 37ce2b9397..3765579a31 100644 --- a/en/docs/reference/customize-product/extending-api-manager/extending-gateway/customizing-api-template-for-gateway.md +++ b/en/docs/reference/customize-product/extending-api-manager/extending-gateway/customizing-api-template-for-gateway.md @@ -6,7 +6,7 @@ An API's gateway configuration file(Synapse configuration) content contains API ## Engaging a custom handler based on API Properties -In API Manager, you can implement and engage custom handlers to customize the default mediation flow of API requests. See [Writing a custom handler]() for more information. The [API properties]({base_path}/learn/design-api/create-api/adding-custom-properties-to-apis/) can be used to conditionally engage these custom handlers for APIs. +In API Manager, you can implement and engage custom handlers to customize the default mediation flow of API requests. See [Writing a custom handler]() for more information. The [API properties]({{base_path}}/design/create-api/adding-custom-properties-to-apis/) can be used to conditionally engage these custom handlers for APIs. Following steps illustrate how you can enable a custom handler for a selected set of APIs which are having a particular property value. @@ -70,11 +70,11 @@ Following steps illustrate how you can enable a custom handler for a selected se !!!Info - If you are using a [distributed API Manager deployment]({base_path}/install-and-setup/deploying-wso2-api-manager/distributed-deployment/understanding-the-distributed-deployment-of-wso2-api-m/) (i.e., Publisher, Devportal, Gateway and Key Manager components are running on separate JVMs), edit the template in the Publisher node. + If you are using a [distributed API Manager deployment]({{base_path}}/install-and-setup/setup/distributed-deployment/understanding-the-distributed-deployment-of-wso2-api-m/) (i.e., Publisher, Devportal, Gateway and Key Manager components are running on separate JVMs), edit the template in the Publisher node. 3. Save the changes. - 4. Add `custom_authentication=true` as an [additional property]({base_path}/learn/design-api/create-api/adding-custom-properties-to-apis/) for those APIs which you need to enable the custom handler. + 4. Add `custom_authentication=true` as an [additional property]({{base_path}}/design/create-api/adding-custom-properties-to-apis/) for those APIs which you need to enable the custom handler. Add Custom Property