# Are web sources able to parse https URLs?

**URL:** https://community.mp3tag.de/t/are-web-sources-able-to-parse-https-urls/15397
**Category:** Web Sources Discussion
**Created:** [January 13, 2014, 9:33pm UTC](https://community.mp3tag.de/t/are-web-sources-able-to-parse-https-urls/15397 "2014-01-13T21:33:03Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![pone](https://community.mp3tag.de/user_avatar/community.mp3tag.de/pone/32/272_2.png) [@pone](https://community.mp3tag.de/u/pone)
#### Post date: [January 13, 2014, 9:33pm UTC](https://community.mp3tag.de/t/are-web-sources-able-to-parse-https-urls/15397/1 "2014-01-13T21:33:03Z")

</div>

Hi Florian, hi Dano, hello all tech experts.

Are web sources able to parse https URLs?

The problem arises at the [google images cover script](https://community.mp3tag.de/t/11166/1), where the old HTTP url directs you to a HTTPS page for some time now, which broke the script. When I try to write the https url into the script via the [IndexUrl]=... line, I get a error message:

"Error connecting to server: ...

> > Invalid URL"

Instead of ... is whatever is written into the [BasedOn]=... line. A line of which I thougt previosly it hasn't any function at all.

SteveHero has [a similar (the same?) problem at trying to modify my soundcloud script](https://community.mp3tag.de/t/8404/19), which also needs the use of https for a working search function.

Is there any known solution? Any ideas?

---

<div class="post-metadata">

### Author: ![dano](https://community.mp3tag.de/user_avatar/community.mp3tag.de/dano/32/6_2.png) [@dano](https://community.mp3tag.de/u/dano)
#### Post date: [January 14, 2014, 4:23pm UTC](https://community.mp3tag.de/t/are-web-sources-able-to-parse-https-urls/15397/2 "2014-01-14T16:23:50Z")

</div>

I don't think it's possible.

---

<div class="post-metadata">

### Author: ![stevehero](https://community.mp3tag.de/user_avatar/community.mp3tag.de/stevehero/32/337_2.png) [@stevehero](https://community.mp3tag.de/u/stevehero)
#### Post date: [January 14, 2014, 7:49pm UTC](https://community.mp3tag.de/t/are-web-sources-able-to-parse-https-urls/15397/3 "2014-01-14T19:49:55Z")

</div>

That's a real pity. What I noticed is that only when you go CTRL+A then view selection source is when you retrieve the info that is what you want to parse. Not that that is any good to find a solution. But just something I picked up on in my trouble shooting.