Apologies, I see now this wasn't my original post, rather on that had been hijacked.

It was a link to an html page reproducing the bug - there was only an image in the page of the opera logo - why on earth do you think there was a hacked/cracked file?

Hello,

I think there maybe a bug in Opera Mini when an image is sized using rem units within a flexbox layout. I've put a sample up here:

https://lamplightdev.com/operamini.html

The expected result is that the Opera logo should be the same dimensions as the box (as is the case in other browsers - including regular Opera). However if you visit the page in Opera Mini, then the image is not resized.

Is there somewhere I can file a bug report?

Many thanks,
Chris.

Thanks Smyru - I will have a look at operamini.page.maxAge as I think that might fix it.

Hello,

I'm developing a site where I am using the common Post/Redirect/Get pattern (https://en.wikipedia.org/wiki/Post/Redirect/Get) when submitting forms. In my particular case this is items for a todo list - so I'm POSTing to say https://site.com/group, processing that request server side adding the new item to a database, and then returning a 302 response (http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.3.3) to indicate the browser should redirect (GET) to https://site.com/group which then displays a list of all the todos submitted to the db. This works on Opera Mini, but on both Opera Mini on Android (v12) and on the microemulator on Mac OSX (I haven't tested on other versions), the resulting page shows the list of todos without the new item, until I refresh the page manually at which point the list returned does include the new item.

I'm assuming what's happening here is that the page being shown after the redirect is the version which has been cached on Opera's proxy server previous to the POST request. If this is the case, is there a way I can indicate to the proxy server that it should display a fresh version of the page from my server rather than the cached version? I have also tried the more correct 303 status code (http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.3.4) but the same thing happens - although the spec says for this:

'The 303 response MUST NOT be cached, but the response to the second (redirected) request might be cacheable'

although I have found no references to how this redirected request can me marked as non-cacheable. Incidentally all other browsers seem not to cache this redirected request at all.

Thanks very much for you help in advance.

Chris.