-
Notifications
You must be signed in to change notification settings - Fork 593
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Routing an IBM AppConnect using Custom path #6321
Comments
Do you want the requests to |
@randmonkey Thanks for the suggestion. IBM AppConnect web page is displaying blank screen after adding the annotation. Can you Please help me here. |
@Rockyjr-git Looks like the URI in the request was not rewritten correctly. Did you enable the |
@randmonkey Rewriteuri is already enabled, IBM AppConnect is working on root path. I am trying to route to other than root path. |
@Rockyjr-git Similar to the example in the doc https://docs.konghq.com/kubernetes-ingress-controller/3.1.x/guides/requests/rewrite-annotation/ , you can define your apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: ace-ingress-rewrite
namespace: appconnect
annotations:
konghq.com/rewrite: "/$1"
konghq.com/strip-path: "true"
spec:
ingressClassName: kong
rules:
- http:
paths:
- path: /~/echo/(\w+)
pathType: ImplementationSpecific
backend:
service:
name: ace-service-7600
port:
number: 7600 |
@Rockyjr-git You need to change |
@Rockyjr-git Your configuration is right. Kong gateway itself is a REVERSE PROXY so configuration of rewrite URI does not affect your request from the browser to Kong gateway. So the URL displayed in your browser is not re-written. You can check the logs of your backend service to check the URI is successfully re-written if the logs are available. |
Is there an existing issue for this?
Current Behavior
I have deployed IBM AppConnect in the Anthos Bare Metal Cluster and Kong Ingress Controller is deployed using Helm chart. I want to route the AppConnect using custom path (/foo) instead of root path (/).
![Screenshot 2024-07-16 180708](https://private-user-images.githubusercontent.com/85946434/349086296-2ca22eb1-9487-46b7-86e8-6bedc0e2b322.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjQ1NjM1NTUsIm5iZiI6MTcyNDU2MzI1NSwicGF0aCI6Ii84NTk0NjQzNC8zNDkwODYyOTYtMmNhMjJlYjEtOTQ4Ny00NmI3LTg2ZTgtNmJlZGMwZTJiMzIyLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA4MjUlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwODI1VDA1MjA1NVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTJkYzM3Yjg5MzhkZDkzZWFkYjcxY2EwODdlN2VmOTYxNDM5OTI1MTljYTk1MWFmZGUxNzdiZjM0ZDMyOTBmY2UmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.Pub1l90UzFdYX3Y47CbKtiW--tXnB3PoiAEwD1yCzs0)
Curl -i http:///Echo is working, but blank is displayed with prefix /Echo. whereas it is working for root path.
Please suggest the steps or any documents for the custom path routing.
Tried using rewrite transformer, but it did not work.
Expected Behavior
Expected to work on the Custom path (/Echo)
Steps To Reproduce
Kong Ingress Controller version
Kubernetes version
v1.27
Anything else?
No response
The text was updated successfully, but these errors were encountered: