But in my case the first request is the Post (with data) as wanted which generates the file on the serverside and delivers Content-Disposition along with the filename.
Opera shows the download dialog.
Then a second request is triggered as a Get (without the Post data obviously) and garbage is downloaded since the server needs at least the originally posted data.

I tried replacing the whole download process by a blob, via adding and removing an "a" link on the fly but there the next Opera Touch appears: the download attribute containing the name of the file is ignored and I end up with files name "(1)", "(2)", etc. without an extension.

Since Opera seems to give a shit on bug reports I'm going to block users with OPT at all as I do with the old IE - on a site with a few 1000 daily users it's a shame but they will blame it on Opera.

To have your problem include in the bug tracking system, you need to use the Report a Problem Tool.

Although people from Opera may reply here eventually, this forum is mainly for users to try to help each other.

Solution? Explanation? Huh?

The explanation is that Opera Touch is broken and needs to be fixed. That also is the solution.

I thought that posting here would act as a way to get issues into the internal bug tracker. Is that not true?

This seems like a waste of time to be honest.

I'll ask again: is there no better path for escalation?

You don't ask anyone. You already posted about your problem and now you wait to see if anyone replies with a solution or explanation.

From times to times you can come here and post to remember the others abou the existence of this topic.

1. It has a "Moderator" flag next to your name which suggests an affiliation of official capacity
2. You responded to the bug report in such a way that suggested an affiliation of official capacity
3. Who else would I ask?

Let's start over: This bug is causing problems. I'd like to see it get fixed. What do you suggest I do. Is there an escalation path I am not aware of?

Thank you very much.

• I reported a bug
• It still exists
• I haven't heard any kind of "Thanks! We'll put this on our list and expect to fix it by XYZ date" or similar

Like, what's the status? Has this been reported in the internal bug tracking system? Has a developer been assigned? Has worked started on the fix? Is there an ETA for the fix to be included in an upcoming release? Etc

Observed behavior:
It downloads an error page (HTML) in place of the actual media file.

Sorry about that, my mistake.

I just upgraded to latest Android 11 and reproduced it.

I can also see different behavior from Chrome and Opera Touch on the server side, OPT clearly makes 2 requests. And the second time it gets a 302 to the error page, of course. There is no way it could work with the current behavior.

This affects anyone using apache module mod_xsendfile, and any other site that deletes-on-get.

Well, I didn't see such message and the file was downloaded. I didn't try to open the file.

And when I tried to use the same link again, I got the message that the file had been removed.