Bugzilla

I have re-investigated. As the result, it looks the difference is caused by the algorithm in the server side. But the reason was different from I told last time.

I checked followings with disabling the http cache.
1. result of the [CSS](https://www.accident-helpline.uk.com/wp-content/cache/autoptimize/css/autoptimize_5a8daa6797e54542e7ecc151006cd0e5.css) when open the [website](https://www.accident-helpline.uk.com/)
2. result when open the CSS with the URL directly
The results of above are not same. And even we get the CSS by curl command using same request headers as 1, the result is not same to 1, but same to 2.

The attachment is a screenshot of both result. The left side is the screenshot of 1, the right side is 2. As we can see, the differences are not only the content size but also the response headers are (Especially `cf-cache-status` ??). Since the `server` field was `cloudflare` the cause might be the algorithm of cloudflare.
Though I have investigated using DevTools on Chrome Canary, the result was same as ours.

Thus, in order to resolve this problem from the root, the DevTools looks like to need to refer the stylesheet which is completely same as that the website referred.
I am thinking the following approaches for now.
1. Make completely same environment of loading the website, then load the stylesheet in DevTools.
2. Keep the loaded content into somewhere(Perhaps, stylesheet object?) , then refers the content from DevTools.
3. Just show an error message which expresses that the content is different.
What do you think?

I have re-investigated. As the result, it looks the difference is caused by the algorithm in the server side. But the reason was different from I told last time.

I checked followings with disabling the http cache.
1. result of the [CSS](https://www.accident-helpline.uk.com/wp-content/cache/autoptimize/css/autoptimize_5a8daa6797e54542e7ecc151006cd0e5.css) when open the [website](https://www.accident-helpline.uk.com/)
2. result when open the CSS with the URL directly

The results of above are not same. And even we get the CSS by curl command using same request headers as 1, the result is not same to 1, but same to 2.

The attachment is a screenshot of both result. The left side is the screenshot of 1, the right side is 2. As we can see, the differences are not only the content size but also the response headers are (Especially `cf-cache-status` ??). Since the `server` field was `cloudflare` the cause might be the algorithm of cloudflare.
Though I have investigated using DevTools on Chrome Canary, the result was same as ours.

Thus, in order to resolve this problem from the root, the DevTools looks like to need to refer the stylesheet which is completely same as that the website referred.
I am thinking the following approaches for now.
1. Make completely same environment of loading the website, then load the stylesheet in DevTools.
2. Keep the loaded content into somewhere(Perhaps, stylesheet object?) , then refers the content from DevTools.
3. Just show an error message which expresses that the content is different.
What do you think?

I have re-investigated. As the result, it looks the difference is caused by the algorithm in the server side. But the reason was different from I told last time.

I checked followings with disabling the http cache.
1. result of the [CSS](https://www.accident-helpline.uk.com/wp-content/cache/autoptimize/css/autoptimize_5a8daa6797e54542e7ecc151006cd0e5.css) when open the [website](https://www.accident-helpline.uk.com/)
2. result when open the CSS with the URL directly

The results of above are not same. And even we get the CSS by curl command using same request headers as 1, the result is not same to 1, but same to 2.

The attachment is a screenshot of both result. The left side is the screenshot of 1, the right side is 2. As we can see, the differences are not only the content size but also the response headers are (Especially `cf-cache-status` ??). Since the `server` field was `cloudflare` the cause might be the algorithm of cloudflare.
Though I have investigated using DevTools on Chrome Canary, the result was same as ours.

Thus, in order to resolve this problem from the root, the DevTools looks like to need to refer the stylesheet which is completely same as that the website referred.
I am thinking the following approaches for now.
1. Make completely same environment of loading the website, then load the stylesheet in DevTools.
2. Keep the loaded content into somewhere(Perhaps, stylesheet object?) , then refers the content from DevTools.
3. Just show an error message which expresses that the content is different.

What do you think?