Jump to content
Updated Privacy Statement

nlffel439

Members
 View Profile  See their activity

  • Posts

    54

  • Joined

  • Last visited

  • Days Won

    1

nlffel439 last won the day on March 5 2022

nlffel439 had the most liked content!

Profile Information

  • User name display option
    User name

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

nlffel439's Achievements

Enthusiast

Enthusiast (6/14)

  • Dedicated Rare
  • Week One Done
  • One Month Later
  • One Year In
  • First Post Rare

Recent Badges

21

Reputation

  1. nlffel439
    I think I also got really lost in the tests I had done over the last few days.
  2. nlffel439
    WOW Thank you Rick for this detailed test. The problem was solved with the help of your configuration example. Many thanks for the support
  3. nlffel439
    I think I can rule out a problem with the WebSocket configuration, I have checked it again and another service on the same CS vServer is also running without problems with WSS. There must be something wrong with the URL rewrite policy.
  4. nlffel439
    First of all, thanks for the answers :) @Rick Davis: Unfortunately the suggestion did not help. Websocket is activatet in the HTTP Profile for this CS vServer @Jeff Riechers: It is the case that the call runs via a non-addressed vServer which is attached to a CS vServer as CS Policy. The service with the backend IP and the port is attached to the non-addressed vServer.
  5. nlffel439 started following Regular expression with URL Transformation , URL Transformation from URL to IP based Path , Maximum characters in GeoLocation Drop Policy reached. and 1 other
  6. nlffel439
    Hi folks, I have a problem with the following scenario on a CS vServer: Input: “any.url.host/Path1/Path2” The backend is also called via websocket Protocol (wss://) Call in the backend “192.168.123.5:8080/Path2” I have tried it so far via a URL Transform URL Policy with two actions I don't want to rule out that I have tried too much and have now lost the overview. But maybe someone else has an idea why the call still doesn't work. Action 1 - Prio 30 Converts the respons from the server back into the required URL in the browser: Action 2 - Prio 60 Convers the request from the Browser into the required Path on the Backend:
  7. nlffel439
    GREAT! Thanks for the quick help The solution with the pattern set was exactly what I was looking for, first test looks promising ! Thanks also for the reference article :)
  8. nlffel439
    Hi folks, I have a problem with a GeoLocation Drop Policy: I would like to add some countries to a DROP policy as an exception. Normally this is no problem, I write the countries with .NOT in the policy and these are then not dropped. For example: add responder policy DROP_non_Test_CUSTOMER "CLIENT.IP.SRC.MATCHES_LOCATION("*.US.*.*.*.*").NOT && CLIENT.IP.SRC.MATCHES_LOCATION("*.CA.*.*.*.*").NOT && CLIENT.IP.SRC.MATCHES_LOCATION("*.GB.*.*.*.*").NOT" DROP However, I now have to create a policy with about 30 countries that should be allowed. And here is the problem of exceeding the maximum number of characters in a policy. With a DROP policy, understandably, no NEXT works so that I can add another one underneath. How could I still add the countries to the selection? Does anyone have any ideas?
  9. nlffel439
    Oh I think I just realized it myself I put && instead of || in the policy Example CLIENT.IP.SRC.MATCHES_LOCATION(\“*.US.*.*.*.*\”) || CLIENT.IP.SRC.MATCHES_LOCATION(\“*.GB.*.*.*.*\”)
  10. nlffel439
    Thank you for the quick reply. :) I just realized now that the NOOP policy does not apply if there is more than one exception in it Example CLIENT.IP.SRC.MATCHES_LOCATION(\“*.US.*.*.*.*\”) && CLIENT.IP.SRC.MATCHES_LOCATION(\“*.GB.*.*.*.*\”) Have I just made a mistake in my thinking?
  11. nlffel439
    Hi folks, I am currently working on a responder policy that triggers a “DROP”. Except for the countries that are defined by “.NOT” Example: Now I would also like to attach a message action, but not for the requests that are dropped, but for those that are allowed. Putting the message action directly into the responder policy is useless here, as it only takes effect when a DROP is triggered. Now the question is, what is the best way to log when one of the IPs excluded from the DROP makes a call?
  12. nlffel439
    Hi, since I was stuck on .REGEX_MATCH all the time to solve the issue, I overlooked that I tested with CONTAINS before and not with "STARTWITH" :/ of course it worked now! Thank you very much :)
  13. nlffel439
    Hi Nicola, thanks for your answer :) In your example, wouldn't the policy also apply if www.testurl.com/path1/path2/api/... would be entered?
  14. nlffel439
    Hi folks, I have the following problem. I have a Contentswitch vServer with a path to www.testurl.com/api/. However, since in the backend the paths following "api" are located directly under root a URL Transformation Responder Policy So far, everything has worked without any problems. Now, however, additional paths have been added for the URL, which are as follows as an example "www.testurl.com/dir/dir2/api/dir3" and this should point to another backend. To avoid having to create a policy for each URL, I simply wanted to tell the old policy via REGEX to only take effect if "/api" comes directly after the hostname. With HTTP.REQ.URL.PATH_AND_QUERY.REGEX_MATCH(re:^\/api\/$:) However, this did not work :( Then I thought ok it is due to the still existing URL transformation policy and have adjusted the URL Transformation Policy: HTTP.REQ.HOSTNAME.EQ("testurl.com") && HTTP.REQ.URL.PATH_AND_QUERY.REGEX_MATCH(re:^\/api\/$:) But unfortunately that didn't work either In summary, the following should work: When testurl.com/api is entered, it lands on backend 1 (Backend 1 has the necessity of URL transformation) if testurl.com/path/path2/api/path3 is entered land on backend 2 Does anyone here have any tips

© Cloud Software Group, Inc. All rights reserved.

×
×
  • Create New...