When I run `wsk -i api list`, there is a error:
```
(serverless) root@dell-1080:/home/dell/tyz/HashCache/serverless-trainticket/src/load-gen/utils# wsk -i api list
error: Unable to obtain the API list: Unable to obtain API(s) from the API Gateway (status code 400): "\r\n400 Request Header Or Cookie Too Large\r\n\r\n

400 Bad Request

\r\nRequest Header Or Cookie Too Large\r\n

---

openresty/1.13.6.2\r\n\r\n\r\n"
```

And everthing seems OK:
```
(serverless) root@dell-1080:/home/dell/tyz/HashCache/serverless-trainticket/src/load-gen/utils# kubectl get all -n openwhisk
NAME READY STATUS RESTARTS AGE
pod/owdev-alarmprovider-59d4cf5db9-j8v9l 1/1 Running 0 65m
pod/owdev-apigateway-66486c84cd-9vjjv 1/1 Running 0 65m
pod/owdev-controller-0 1/1 Running 0 65m
pod/owdev-controller-1 1/1 Running 0 65m
pod/owdev-couchdb-696d7db9bb-srjxk 1/1 Running 0 65m
pod/owdev-gen-certs-7gr5q 0/1 Completed 0 65m
pod/owdev-init-couchdb-mghrf 0/1 Completed 0 65m
pod/owdev-install-packages-6rj6m 0/1 Completed 0 65m
pod/owdev-invoker-0 1/1 Running 0 65m
pod/owdev-invoker-1 1/1 Running 0 65m
pod/owdev-kafka-0 1/1 Running 0 65m
pod/owdev-kafkaprovider-7448f78f57-rs948 1/1 Running 0 65m
pod/owdev-nginx-7b4b46485-b5pfc 1/1 Running 0 65m
pod/owdev-redis-685cd564d8-tjxfl 1/1 Running 0 65m
pod/owdev-wskadmin 1/1 Running 0 65m
pod/owdev-zookeeper-0 1/1 Running 0 65m
pod/wskowdev-invoker-00-32-whisksystem-deleteapi 1/1 Running 0 11m
pod/wskowdev-invoker-00-33-prewarm-nodejs10 1/1 Running 0 7m41s
pod/wskowdev-invoker-11-32-prewarm-nodejs10 1/1 Running 0 7m38s
pod/wskowdev-invoker-11-8-whisksystem-getapi 1/1 Running 0 42m

NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/owdev-apigateway ClusterIP 10.109.85.152 8080/TCP,9000/TCP 65m
service/owdev-controller ClusterIP 10.102.187.76 8080/TCP 65m
service/owdev-couchdb ClusterIP 10.99.67.138 5984/TCP 65m
service/owdev-etcd ClusterIP 10.107.190.93 2379/TCP 65m
service/owdev-kafka ClusterIP None 9092/TCP 65m
service/owdev-nginx NodePort 10.107.87.6 80:30036/TCP,443:31001/TCP 65m
service/owdev-redis ClusterIP 10.97.167.99 6379/TCP 65m
service/owdev-zookeeper ClusterIP None 2181/TCP,2888/TCP,3888/TCP 65m

NAME READY UP-TO-DATE AVAILABLE AGE
deployment.apps/owdev-alarmprovider 1/1 1 1 65m
deployment.apps/owdev-apigateway 1/1 1 1 65m
deployment.apps/owdev-couchdb 1/1 1 1 65m
deployment.apps/owdev-kafkaprovider 1/1 1 1 65m
deployment.apps/owdev-nginx 1/1 1 1 65m
deployment.apps/owdev-redis 1/1 1 1 65m

NAME DESIRED CURRENT READY AGE
replicaset.apps/owdev-alarmprovider-59d4cf5db9 1 1 1 65m
replicaset.apps/owdev-apigateway-66486c84cd 1 1 1 65m
replicaset.apps/owdev-couchdb-696d7db9bb 1 1 1 65m
replicaset.apps/owdev-kafkaprovider-7448f78f57 1 1 1 65m
replicaset.apps/owdev-nginx-7b4b46485 1 1 1 65m
replicaset.apps/owdev-redis-685cd564d8 1 1 1 65m

NAME READY AGE
statefulset.apps/owdev-controller 2/2 65m
statefulset.apps/owdev-invoker 2/2 65m
statefulset.apps/owdev-kafka 1/1 65m
statefulset.apps/owdev-zookeeper 1/1 65m

NAME COMPLETIONS DURATION AGE
job.batch/owdev-gen-certs 1/1 18s 65m
job.batch/owdev-init-couchdb 1/1 7m10s 65m
job.batch/owdev-install-packages 1/1 8m34s 65m

```

Start by reproducing `wsk -i api list` and inspecting the API Gateway and nginx behavior for the reported 400 response. Compare the request headers or cookies with the gateway configuration; done means identifying the cause and verifying that API listing succeeds after the appropriate configuration or deployment change.

Written by the indexing model from the issue text.