SoundCloud API redirecting to https stream URL - http

since a few days Soundcloud seems to be redirecting the stream urls all to https stream links. Since our project is reworking the soundcloud responses for streaming devices, which do not support streaming over https I want to find out how to get the http stream url.
It does not matter if I call https:// api.soundcloud.com/tracks/9479080/stream or http:// api.soundcloud.com/tracks/9479080/stream?
both versions redirect to a https streaming url. If I resolve the streaming URL before, it just does not work sometimes. (get http 401 error),
Please help

Related

How can I make a website partially unsecure?

I have a website that uses HTTPS so it is secure by default.
I am aiming to send some HTTP requests from the website, but the problem is that modern versions of web browsers do not allow the use of HTTP requests inside of HTTPS sites.
So, what I am trying to do here is to make a portion of my website un-secure using HTTP instead of HTTPS, so that I can send the requests I want.
Is that possible?
If there are any other suggestions to send HTTP requests, please help me with it.

If a domain is secured with HTTPS, does it become less secure if the URL is typed using HTTP?

For example, does the URL http://www.google.com/ make the URL less safe, even though the default for this domain is with https?
Accessing a site using http:// (thus the unprotected unecrypted HTTP protocol) means that at least one unprotected HTTP request is sent to the server (most sites that support https will automatically redirect you to the https version).
This unprotected request can be intercepted by an attacker and thus send you arbitrary data back (malicious JavaScript code, redirect to other sites and so on).
The only exception is if you type http://www.google.com/ and you are using Chrome browser because Chrome will for addresses on google.com automatically change the entered URL to https:// before anything is sent on the network.

Http request automatically becomes https

I'm running an asp.net core web application secured by ssl.
I need to send an ajax request to a local-network device which does not offer https.
So I try to send an ajax http request to a local ip adress (eg. http://192.168.1.30/hello-world) from a https browser window showing my web-app.
The url of the ajax request always gets converted into https://192.168.1.30/hello-world (which does not exist).
Is there anyway to avoid this? The device does not offer https and I can't send a local request from an insecured source.
Thank you!

how to play http live streaming video URL in jwplayer on my https website?

I am newb for jwplayer.
I have issue to play http live streaming video URL on my https website.
I have following live streaming video URL
http://xyz.3da92.cdn.net/803DA92/abcd/v/RA/abcdxyz/play.m3u8?xyz
and my website like https://example.com with has jwplayer.
but when I have try to play live streaming
I am getting following:
Mixed Content: The page at 'https://example.com' was loaded over HTTPS,
I am not able to change live streaming video URL becuse it is third party URL So, I can't control it. And want to run my website on https.
So, My question is how to play http live streaming video URL on my https website?
Proxy the stream on your server to output https.

Load https site in iframe on http site

We want to load a page of our platform into an iframe on a client site. Our platform contains a SSL certificate and runs always on HTTPS. The client's site runs on HTTP.
The URL that get's loaded into the iframe contains URL params for the name of the user. Are these url parameters send encrypted because the site in the iframe is HTTPS or are they accessible because the the parameters are created on the client HTTP site?
Short example:
Client site (HTTP) loads iframe with url "https://oursite.com/?firstname=Bob&lastname=Forrest". Are the URL parameters encrypted when they are transferred to the iframe site?
Thanks in advance.
The URL parameters will get encrypted. SSL sits between the HTTP and TCP layers, so the browser will first establish a TCP connection to the server before any data is exchanged. All data (including the request with the URL parameters) will be encrypted.
It is still generally advised to not pass sensitive information in the URL, as it will most likely get stored in plain text in the server logs.

Resources