How to secure POST, PUT and DELETE but not GET? #1988
-
|
I really would like to know if I am doing it correctly. I want to secure POST, PUT and DELETE but not GET, I would like to leave GET with no need for authentication. Is that how to do it? also, how can I avoid the reputation of the repeated attributes? Do I need to have GlobalConfiguration and how to do it?
Update by MaintainerPlease remove this large picture 👆 and insert JSON text! |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 3 replies
-
Just don't define the verb! Note, your UpstreamPathTemplate of the second route includes the template of the first one. Final config depends on your services. I can't recommend on the config more. Please finish your setup by your own!
Sorry? I don't understand you. There is no ability to join routes or define route families... You must define exactly the same props of route configuration!
How to do it, what? To define classic routes you needn't use global configuration at all. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you i got you |
Beta Was this translation helpful? Give feedback.
-
|
I have one more question please, is there is any plans to officially add support for Swagger? I know there is this package but just wondering? |
Beta Was this translation helpful? Give feedback.
-
|
Yes, there are plans!
|
Beta Was this translation helpful? Give feedback.
Just don't define the verb!
Or, define 2 different routes with different upstream methods, but upstream templates can be the same.
1st route is authenticated, and the 2nd one is anonymous.
Note, your UpstreamPathTemplate of the second route includes the template of the first one.
/notification/{everything}contains/notification/deviceFinal config depends on your services. I can't recommend on the config more. Please finish your setup by your own!
Sorry? I don't understand you. There is no…