Skip to main content
Solved

End users getting Error 400 or Error 502 using IFS Cloud

  • February 6, 2024
  • 1 reply
  • 434 views

IWAHANS
Sidekick (Customer)
Forum|alt.badge.img+7
  • Sidekick (Customer)
  • 29 replies

Some end users are getting Error 400 and Error 502 when opening an additional tab with IFS Cloud in both Edge and Chrome.

This is now happening to more users. They have cleared browser history/cache to no avail.

Is there anyone that has had similar issues like this in Cloud?

Br hans

Best answer by hhanse

Yes - we have seen this.
The root cause is that something (other than IFS) add cookies to the requests sent to IFS.
You can record a HAR file in you browser when the error happens. There you can see which cookies are large. Try to figure out which ones comes from non IFS origin (e.g loadbalancer cookies and network identity cookies)
IFS cloud in later SU’s later than 6months or so should be able to handle 16k of headers older version only handle 8k which is enough to handle the IFS cookies.
We have also seen that if the Remote infrastucture is old, then the patch to increase from 8k to 16k don’t get fully applied. 
 
Helm version on management server need to be > ~3.10

look in the ingress config:
kubectl get ingress ifs-sticky-ingress -o yaml -n <namespace>

you should find:
    nginx.ingress.kubernetes.io/server-snippet: |
        large_client_header_buffers 4 16k;


 

View original
Did this topic help you find an answer to your question?

1 reply

Forum|alt.badge.img+10
  • Hero (Employee)
  • 175 replies
  • Answer
  • February 7, 2024

Yes - we have seen this.
The root cause is that something (other than IFS) add cookies to the requests sent to IFS.
You can record a HAR file in you browser when the error happens. There you can see which cookies are large. Try to figure out which ones comes from non IFS origin (e.g loadbalancer cookies and network identity cookies)
IFS cloud in later SU’s later than 6months or so should be able to handle 16k of headers older version only handle 8k which is enough to handle the IFS cookies.
We have also seen that if the Remote infrastucture is old, then the patch to increase from 8k to 16k don’t get fully applied. 
 
Helm version on management server need to be > ~3.10

look in the ingress config:
kubectl get ingress ifs-sticky-ingress -o yaml -n <namespace>

you should find:
    nginx.ingress.kubernetes.io/server-snippet: |
        large_client_header_buffers 4 16k;


 


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings