I'm unable to reproduce this problem in our demos. If there is a connection between the requests for favicon and bus messages, it looks like favicons are loaded after each bus request completes. Can you tell me anything about what these bus requests are doing on the client side? Are you perhaps navigating to a different url? Maybe you're using code splitting and these favicon downloads happen from code fragments being loaded into iframes?
I'm not really sure what's going on here, but I think there must be some other action coinciding with a bus request finishing that causes this.
Hi Max, thanks for the quick response.
We don't have the application inside an iframe, and we don't navigate on those requests. We use the bus for several things, a heartbeat, sending messages and do stuff about that, etc. Ok, I'll keep digging into this then. Let me know if you have any other clue on why the requests could be doing this.