Definitely was not fixed for us on version 6.1.3.
Browser is attempting to access assets within the "/static/app/maps/img" folder. Offending entries are found within all of the url(...) calls within splunk/etc/apps/maps/appserver/modules/GoogleMaps/GoogleMaps.css
In our case, we couldn't change these to be absolute paths that go through the proxy since we have multiple search heads, and so that path would be different depending upon the current user.
To fix: I found inserting "../.." ahead of the first slash for all of the "url(...)" entries did the trick; the GoogleMaps app presents itself via a URL that is two folders deeper than the 'static' folder, so the browser just needs to "back-up" two levels before trying to access "/static/app/maps/img/*".
I can't be sure this will survive any updates to the GoogleMaps app... but hopefully Splunk/Google will notice this fix and include it within the official version.
... View more