[Interest] IFW issue: HTTP request returns a Not Acceptable

[coroberti .]

On Tue, Sep 18, 2018 at 9:59 AM, Kai Koehne <Kai.Koehne at qt.io> wrote:
>
>
>> -----Original Message-----
>> From: Interest <interest-bounces+kai.koehne=qt.io at qt-project.org> On
>> Behalf Of Kevin Wang
>> Sent: Tuesday, September 18, 2018 1:33 AM
>> To: Qt Project <interest at qt-project.org>
>> Subject: [Interest] IFW issue: HTTP request returns a Not Acceptable
>>
>> Hi All,
>>
>>
>> I am attempting to utilize the Qt Installer Framework for our company's
>> software. I am just starting out and am running into some issues.
>>
>> I uploaded the generated repo to our website, and linked the repo in the
>> installer. When I run the installer and attempt to fetch the remote repo tree,
>> it returns this:
>>
>>
>>       "Cannot retrieve remote tree. "
>> [...]
>> I sniffed out the HTTP request and it showed that the IFW sent this:
>>       GET /downloads/onlinesoftwarerepo/Updates.xml?-915259074
>> HTTP/1.1
>>       Connection: Keep-Alive
>>       Accept-Encoding: gzip, deflate
>>       Accept-Language: en-US,*
>>       User-Agent: Mozilla/5.0
>>       Host: www.spikegadgets.com <http://www.spikegadgets.com>
>>
>> So I have absolutely no experience in web servers and HTTP requests and
>> such. The website and FTP was set up for us, which I used to upload the repo.
>> To me, the issue seems to be that the Installer framework is sending a HTTP
>> request for an encoding that doesn't make sense ("Accept-Encoding: gzip,
>> deflate" for a .xml file?).
>
> An xml file can be compressed , too 😊 Accept-Encoding is just a hint
> to the server which compression the client accepts, and the server is free to
> ignore it. So I doubt that's the issue.
>
> My guess is the "?-915259074 " part of the url is what makes the server fail.
> IIRC this was added to the request in IRC to work around some caching issues,
>  but should be ignored by the server. Maybe that doesn't work for yours.
>
> Regards
>
> Kai

Hi,
To prevent caching, you may wish instead to add header:
Cache-Control: no-store

It should be enough, but you can add also:
Cache-Control: no-cache, private

Kind regards,
Robert Iakobashvili
............................