Replies: 4 comments 4 replies
-
@tntstn as far as i can remeber, this trailing slash issue is known since 3-4 years, and i have looked at that time if there are any malformed requests or not - I don't think that there are any, but if you encounter some, please tell |
Beta Was this translation helpful? Give feedback.
-
Hi all, When I checked the source code (3.23.0 - latest) manually, I encountered it in three places, I am not sure if they are valid, please correct me if I'm wrong.
|
Beta Was this translation helpful? Give feedback.
-
we could add in the implementations of HttpAction a check which just removes the trailing slash if there is one. mindconnect-nodejs/src/api/frontend-auth.ts Line 112 in bca2183 mindconnect-nodejs/src/api/browser-auth.ts Line 155 in bca2183
|
Beta Was this translation helpful? Give feedback.
-
The billboard urls are correct btw - take a look here - it seems that the insights hub rules about trailing slash have not been verified against insights hub own APIs ;) cc: @gesslinger |
Beta Was this translation helpful? Give feedback.
-
I have a question and need an answer immediately. There is a restriction which is defined in insightshub (Insights Hub Release Notes mention change in AssetManager api behaviour) release document. In this document, basicly it says "If there is any usage at the end of the requests with backslash / , it should be removed ". As you see below, there is no backslash at the end of the request explained under well-formed requests.
Currently, we are using "@mindconnect/mindconnect-nodejs": "3.22.0". I need to know, is there any usage in this version or if there is an usage in any version, which version is the proper to upgrade?
Examples of malformed requests:
GET https://gateway.\Unknown macro: {region}-{environment}.{domain}/api/.../v3/.../{Id}/{Name}/
Examples of well-formed requests:
GET https://gateway.\Unknown macro: {region}-{environment}.{domain}/api/.../v3/.../{Id}/{Name}
Beta Was this translation helpful? Give feedback.
All reactions