I have a project in the works that I had queried here about recently. Those issues have been solved. But I am up against my next barricade: I have a css background rule that is set to a url. Normally this would be a path to an image file. But I have it set to a get query. The page is a self processing php page and has code to process the get query and use gd to serve the image file. This approach is being used for background tile and to set a div element background. This is a single instance (css no-repeat). The tile is just that, repeated across the entire page. The div element background is being properly processed and the image does show up. The tile image is requested and is served. BUT three of the browsers I have to test with will not display the background tile in the page even though they have it to hand. They are Firefox, Chrome, Opera it will show up as a vignette in FIrefox dev tools ( mouse hovers over the get query string displayed for the entry in the network panel and a popout shows the image). I also have Safari and it WILL display the background tile in the page. This request header is the only difference I can see: Sec-Fetch-Mode:no_cors Why might it make a difference? according to the Mozilla site this request header is NOT supported by Safari, while Firefox, Chrome and Opera DO support it. Since this is a request header, is there any special consideration that php may be giving it? Or could Apache be dealing with it directly? I have had my web site down without a hosting service. But from a request from a forum post response I am in the process of setting up a new hosting service. AS soon as it is set up and I post the project as a demo I can provide a link to it. Thank you for time and attention; JK
