Good afternoon:
We have noticed for some time that the logo sometimes fails to load on the first call.
As example:
![]()
![]()
Has anyone else experienced this problem?
Hmm, yes, I'm seeing the same:
![]()
It's failing on https://dataverse.harvard.edu/logos/navbar/logo.png;jsessionid=ae10addf4895c024c26deeaee3d6 for me
% curl -i 'https://dataverse.harvard.edu/logos/navbar/logo.png;jsessionid=ae10addf4895c024c26deeaee3d6'
HTTP/2 202
server: awselb/2.0
date: Thu, 18 Jun 2026 13:19:52 GMT
content-length: 0
x-amzn-waf-action: challenge
cache-control: no-store, max-age=0
content-type: text/html; charset=UTF-8
access-control-allow-origin: *
access-control-max-age: 86400
access-control-allow-methods: OPTIONS,GET,POST
access-control-expose-headers: x-amzn-waf-action
x-amzn-waf-action is our AWS ELB (Elastic Load Balancer).
After refresh:
![]()
Ok, so you're seeing this without the ELB. Hmm.
It must have something to do with the jsessionid, right? It appears in the URL for the first load in an incognito window, for example.
Right
It seems to happen only in the latest versions.
It works fine from a fresh docker compose env: https://guides.dataverse.org/en/6.10.1/container/running/demo.html#quickstart
This environment only has Payara, though, so when I go to http://localhost:8080 I'm not hitting any sort of proxy like Apache.
![]()
Does the problem only surface when a proxy is in the mix? How can I reproduce this on my laptop? :thinking:
@Daniel Vila please feel free to create an issue about this at https://github.com/IQSS/dataverse/issues
I can definitely see the problem at https://edmond.mpg.de
![]()
Last updated: Aug 18 2026 at 08:27 UTC