https://rs.hpkg.tv/ - Links in remote scheduling email no longer working

[Black Hole]

The links embedded in the email are fully formed and in a shorthand format that should be turned to longhand on the rs server.

:sigh:

That's as may be, but the browser is involved in the transaction.

The relevant parts:

Those are protocol-relative URLs which are discouraged these days but they were once the de-facto way to reference CDNs like code.jquery.com

there's no reason not to change them, and I've done that.

If you need a translation, that means standards have moved on and the RS has been updated to make it compliant. The links it sends out in emails will have a different format now. If you keep trying to use the old format links without changing anything at your end (ie the browser) you'll keep hitting the same problem.

 

[prpr]

The links it sends out in emails will have a different format now.

I'm not sure that's true, but I haven't seen any. The old redirections still work the same.
The links for the jquery stuff have been updated to make them non-ambiguous compared to before by inserting "https:".

<script type=text/javascript src="https://code.jquery.com/jquery-1.12.4.min.js"></script>
<script type=text/javascript src="https://code.jquery.com/jquery-migrate-1.2.1.min.js"></script>
<script type="text/javascript" src="https://code.jquery.com/ui/1.11.4/jquery-ui.min.js"></script>

 

[af123]

The links for the jquery stuff have been updated to make them non-ambiguous compared to before by inserting "https:".

They were never ambiguous, they were protocol-relative, so the browser would use the appropriate protocol depending on that which was used to load the containing page. Unfortunately not all browsers follow standards (RFC 3986) but I'm also not sure how this can be the reason for the 404 errors.

I'm not sure that's true, but I haven't seen any. The old redirections still work the same.

Correct, the links have not changed.

If somebody can reproduce this error, and post the exact time the error occurred, I can go and look in the logs and see what is happening.

 

[Black Hole]

Okay, I'll take back (some of) what I said. 404 is definitely confusing matters.

 

[trog]

16.13

 

[af123]

16.13

Thanks, that was useful. Is it any better now?
I think this is your browser transparently upgrading the request from http://hpkg.tv/xSeven+Years+In+Tibet to https://hpkg.tv/xSeven+Years+In+Tibet because apparently that's what people always want.

Both work now:

hummy# curl -i http://hpkg.tv/xSeven+Years+In+Tibet
HTTP/1.1 301 Moved Permanently
Server: nginx
Date: Mon, 23 Oct 2023 15:37:08 GMT
Content-Type: text/html
Content-Length: 162
Connection: keep-alive
Location: https://rs.hpkg.tv/epg_search.html?pterm=Seven+Years+In+Tibet

hummy# curl -i https://hpkg.tv/xSeven+Years+In+Tibet
HTTP/2 301
server: nginx
date: Mon, 23 Oct 2023 15:35:45 GMT
content-type: text/html
content-length: 162
location: https://rs.hpkg.tv/epg_search.html?pterm=Seven+Years+In+Tibet

 

[trog]

Thanks, that was useful. Is it any better now?
I think this is your browser transparently upgrading the request from http://hpkg.tv/xSeven+Years+In+Tibet to https://hpkg.tv/xSeven+Years+In+Tibet because apparently that's what people always want.

Both work now:

hummy# curl -i http://hpkg.tv/xSeven+Years+In+Tibet
HTTP/1.1 301 Moved Permanently
Server: nginx
Date: Mon, 23 Oct 2023 15:37:08 GMT
Content-Type: text/html
Content-Length: 162
Connection: keep-alive
Location: https://rs.hpkg.tv/epg_search.html?pterm=Seven+Years+In+Tibet

hummy# curl -i https://hpkg.tv/xSeven+Years+In+Tibet
HTTP/2 301
server: nginx
date: Mon, 23 Oct 2023 15:35:45 GMT
content-type: text/html
content-length: 162
location: https://rs.hpkg.tv/epg_search.html?pterm=Seven+Years+In+Tibet

Only just seen your reply and can confirm that it now works on my Windows 8.1 Opera 95 laptop. I have the HTTPS everywhere app installed on my Opera if that's worth knowing.

 

[Suzandii]

Thanks, that was useful. Is it any better now?
I think this is your browser transparently upgrading the request from http://hpkg.tv/xSeven+Years+In+Tibet to https://hpkg.tv/xSeven+Years+In+Tibet because apparently that's what people always want.

Both work now:

hummy# curl -i http://hpkg.tv/xSeven+Years+In+Tibet
HTTP/1.1 301 Moved Permanently
Server: nginx
Date: Mon, 23 Oct 2023 15:37:08 GMT
Content-Type: text/html
Content-Length: 162
Connection: keep-alive
Location: https://rs.hpkg.tv/epg_search.html?pterm=Seven+Years+In+Tibet

hummy# curl -i https://hpkg.tv/xSeven+Years+In+Tibet
HTTP/2 301
server: nginx
date: Mon, 23 Oct 2023 15:35:45 GMT
content-type: text/html
content-length: 162
location: https://rs.hpkg.tv/epg_search.html?pterm=Seven+Years+In+Tibet

Works now on Android Chrome & Edge and Windows 10 Chrome, Edge and Firefox - Many thanks for persevering .

Any chance of fixing the missing channel icons by linking up with David500 on AVForums as I mentioned in post #15. Also, do you have the ability to amend the "Conflict Found" email to include a link to the conflicts page (Visual button)?