How to modify route provided by plugin

[Mr-EmPee]

The plugin openid-connect provides an internal route "/logout" but I want to modify the response headers of that route how do i do it?

The first thing I tried was

routes:
  -
    uri: /logout
    service_id: apisix
    plugins:
      response-rewrite:
        headers:
          set:
            Clear-Site-Data: "\"cache\",\"cookies\",\"storage\""

But when I try to logout there is now an error:

From the logs it also seems that it goes into a loop?

MORE ....

apisix_1         | 172.24.1.101 - - [23/Dec/2024:10:27:20 +0000] 172.17.0.149:9443 "GET /logout HTTP/1.1" 400 305 1.249 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:133.0) Gecko/20100101 Firefox/133.0" 0.0.0.0:9443 400 1.249 "https://172.17.0.149:9443"
apisix_1         | 172.24.1.101 - - [23/Dec/2024:10:27:20 +0000] 172.17.0.149:9443 "GET /logout HTTP/1.1" 400 305 1.255 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:133.0) Gecko/20100101 Firefox/133.0" 0.0.0.0:9443 400 1.255 "https://172.17.0.149:9443"
apisix_1         | 172.24.1.101 - - [23/Dec/2024:10:27:20 +0000] 172.17.0.149:9443 "GET /logout HTTP/1.1" 400 305 1.263 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:133.0) Gecko/20100101 Firefox/133.0" 0.0.0.0:9443 400 1.263 "https://172.17.0.149:9443"
apisix_1         | 172.24.1.101 - - [23/Dec/2024:10:27:20 +0000] 172.17.0.149:9443 "GET /logout HTTP/1.1" 400 305 1.265 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:133.0) Gecko/20100101 Firefox/133.0" 0.0.0.0:9443 400 1.265 "https://172.17.0.149:9443"
apisix_1         | 172.24.1.101 - - [23/Dec/2024:10:27:20 +0000] 172.17.0.149:9443 "GET /logout HTTP/1.1" 400 305 1.277 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:133.0) Gecko/20100101 Firefox/133.0" 0.0.0.0:9443 400 1.277 "https://172.17.0.149:9443"
apisix_1         | 172.24.1.101 - - [23/Dec/2024:10:27:20 +0000] 172.17.0.149:9443 "GET /logout HTTP/1.1" 400 305 1.327 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:133.0) Gecko/20100101 Firefox/133.0" 0.0.0.0:9443 400 1.327 "https://172.17.0.149:9443"
apisix_1         | 172.24.1.101 - - [23/Dec/2024:10:27:20 +0000] 172.17.0.149:9443 "GET /logout HTTP/1.1" 400 305 1.329 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:133.0) Gecko/20100101 Firefox/133.0" 0.0.0.0:9443 400 1.329 "https://172.17.0.149:9443"
apisix_1         | 172.24.1.101 - - [23/Dec/2024:10:27:20 +0000] 172.17.0.149:9443 "GET /logout HTTP/1.1" 400 305 1.336 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:133.0) Gecko/20100101 Firefox/133.0" 0.0.0.0:9443 400 1.336 "https://172.17.0.149:9443"
apisix_1         | 172.24.1.101 - - [23/Dec/2024:10:27:20 +0000] 172.17.0.149:9443 "GET /logout HTTP/1.1" 400 305 1.397 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:133.0) Gecko/20100101 Firefox/133.0" 0.0.0.0:9443 400 1.397 "https://172.17.0.149:9443"
apisix_1         | 172.24.1.101 - - [23/Dec/2024:10:27:20 +0000] 172.17.0.149:9443 "GET /logout HTTP/1.1" 400 305 1.413 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:133.0) Gecko/20100101 Firefox/133.0" 0.0.0.0:9443 400 1.413 "https://172.17.0.149:9443"
apisix_1         | 172.24.1.101 - - [23/Dec/2024:10:27:20 +0000] 172.17.0.149:9443 "GET /logout HTTP/1.1" 400 305 1.426 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:133.0) Gecko/20100101 Firefox/133.0" 0.0.0.0:9443 400 1.426 "https://172.17.0.149:9443"

MORE ....

[dosubot[bot]]

Hey @Mr-EmPee! I'm here to help you with your technical questions and bug fixes while you wait for a human maintainer. Let's solve this together!

A similar issue was discussed in a closed thread titled "Request Header Fields Too Large. StatusCode: 431" ^[1]. Although it doesn't provide a solution, it might be related to the problem you're experiencing with large headers or cookies.

The "400 Bad Request" error you're encountering, along with the loop in the logs, suggests that there might be a misconfiguration causing repeated requests. This can happen if the response-rewrite plugin or another configuration is inadvertently causing a redirect loop or if the headers are indeed too large.

To address the loop and the "Request Header Or Cookie Too Large" error, consider the following steps:

1. Check for Redirect Loops: Ensure that there are no plugins or configurations that might be causing a redirect loop. This can happen if the response-rewrite plugin or another plugin is modifying headers in a way that triggers repeated requests.

2. Header Size Limits: APISIX, built on OpenResty, inherits NGINX's default header size limits. You might need to increase the client_header_buffer_size and large_client_header_buffers settings in your NGINX configuration to handle larger headers.

3. Review Plugin Configuration: Double-check the response-rewrite plugin configuration to ensure it is correctly set up and not causing unintended behavior. Make sure the headers being set do not exceed typical size limits.

4. Debugging: Use logging to trace the flow of requests and identify where the loop might be occurring. This can help pinpoint if a specific plugin or configuration is causing the issue.

By addressing these areas, you should be able to resolve the loop and the header size issue.

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other}

[Mr-EmPee]

It doesn't make sense that it throws an error of type "header or cookie too large", response-rewrite is modifying the response not the request that is processed by openresty