Header Too Large in sas studio app pod log

[srinivasa_attot]

Hi All,

I have deployed SAS VIYA on Kubernetes and all the pods are running except CAS pods. when i am trying to SASStuudio url it gives an error" bad request". 

Note: I am not able to open any of the url lie studio, drive  and Environment manager.

On checking SAS-Studio-app pod log, i see the error " Header too large". 

Can anyone help me how to fix the header issue ?

Regards,
Srinivas

[srinivasa_attot]

Error details:

"version":1,"timeStamp":"2025-02-26T01:58:54.667Z","level":"info","source":"sas-studio-app","message":"Error parsing HTTP request header\n Note: further occurrences of HTTP request parsing errors will be logged at DEBUG level.\njava.lang.IllegalArgumentException: Request header is too large\n\tat org.apache.coyote.http11.Http11InputBuffer.fill(Http11InputBuffer.java:777)\n\tat org.apache.coyote.http11.Http11InputBuffer.parseHeader(Http11InputBuffer.java:971)\n\tat org.apache.coyote.http11.Http11InputBuffer.parseHeaders(Http11InputBuffer.java:592)\n\tat org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:293)\n\tat org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:63)\n\tat org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:905)\n\tat org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1741)\n\tat org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:52)\n\tat org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1190)\n\tat org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:659)\n\tat org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:63)\n\tat java.base/java.lang.Thread.run(Thread.java:1583)\n","properties":{"logger":"org.apache.coyote.http11.Http11Processor","thread":"http-nio-10445-exec-8"}}

{"version":1,"timeStamp":"2025-02-26T02:19:22.965Z","level":"info","source":"sas-studio-app","message":"[FEATURE_FLAGS_LIBRARY_COMMUNICATIONS_ERROR_POST_CONNECT] The feature flags library has lost communication with the feature flags service. The status code is 401 UNAUTHORIZED.","properties":{"logger":"com.sas.commons.features.UnleashErrorLogger","thread":"unleash-api-executor"},"messageKey":"com.sas.commons.features.LogMessages.FEATURE_FLAGS_LIBRARY_COMMUNICATIONS_ERROR_POST_CONNECT","messageParameters":{"0":"401 UNAUTHORIZED"}}

[gwootton · Accepted solution]

I think this can happen if the authenticating user is a member of enough groups to cause your oauth token to breach the maximum header size configured for Java services (server.max-http-header-size).

Are you able to log in to Viya as sasboot successfully?

If so, under Env Mgr > Configuration > Definitions locate the "server" definition and see if you have an existing definition for the Global service. If so, edit that definition and if not, create a new configuration, selecting the service Global.

Then add a property called "max-http-header-size" with a value of "32768", and save the configuration.

If you aren't able to log in to Viya you can add this configuration in the SAS Configuration Server directly with the command:

kubectl -n namespace exec -it sas-rabbitmq-server-0 -c sas-rabbitmq-server -- /opt/sas/viya/home/bin/sas-bootstrap-config kv write config/application/server/max-http-header-size 32768 --force

You may need to restart your Viya Java-based services to pick up this change.

You can get a list of those services using:
kubectl -n namespace get deploy -o jsonpath='{range .items[?(@.spec.template.metadata.annotations.sas\.com/kustomize-base=="spring")]}{.metadata.name}{"\n"}{end}'

[srinivasa_attot]

Thank you @gwootton .  I am still not able to login to SAS VIYA environment manger but after executing kubectl commands the error is not seen in the logs.

[gwootton]

Are you able to authenticate using the /SASLogon endpoint?

[srinivasa_attot]

Thanks for your help. Yes, I am able to authenticate.