eztv.tf | eztvstatus.org
Search title:  
TV Packs only
 
   RSS Status

Username:

Password:

Login Register
[ Forum » Admin's Corner » Thread ]

Please login to reply
[#169012] Written by: Dungogvolts [16/10/2011, 18:52]
its gone again.... this is a real pain it was working so well. why does it do this??????????
[#169082] Written by: wisem2540 [17/10/2011, 14:17]
any update as to when the rss feed will be back up?
[#169249] Written by: Tuttle [19/10/2011, 20:10]
actually it is working, but...

since it can no longer be reached as http:// but only as feed:// some bittorrent clients/plugins can no
longer use it <sigh>

as an example i use scanerss inside vuze and it cannot handle feed:// addresses but only http://
ones.

it was working up to sunday 16/10, but then some modification/update removed the http:// access and
made it unusable for some of us. last reported successful access i have is on monday at 00:08 hour
(central europe time zone - cest).


please, please, make it once again accessible as http://www.ezrss.it/feed/ as it was up to a few days
ago (and as is written in the setup instructions examples), or else it becomes unusable for some of us.
thank you.

[#169275] Written by: NovaKing (Administrator) [20/10/2011, 05:58]
Quote by tuttle
actually it is working, but...

since it can no longer be reached as http:// but only as feed:// some bittorrent clients/plugins
can no
longer use it <sigh>

as an example i use scanerss inside vuze and it cannot handle feed:// addresses but only http://
ones.

it was working up to sunday 16/10, but then some modification/update removed the http:// access and
made it unusable for some of us. last reported successful access i have is on monday at 00:08 hour
(central europe time zone - cest).


please, please, make it once again accessible as http://www.ezrss.it/feed/ as it was up to a few
days
ago (and as is written in the setup instructions examples), or else it becomes unusable for some of
us.
thank you.



it appears to be working fine? i am unsure what you are currently experiencing. we did migrate
ezrss to the new servers, but that downtime didn't last too long.
[#169283] Written by: Tuttle [20/10/2011, 09:19]
Quote by novaking

it appears to be working fine?

i believe it is. if i access it from a web browser i can see it's regularly updated.

Quote by novaking

i am unsure what you are currently experiencing. we did migrate
ezrss to the new servers, but that downtime didn't last too long.

let me try explaining in more detail:

the address for the feed is: feed://www.ezrss.it/feed/ my web browsers can handle that properly.

if i try putting that in scanerss (plugin in vuze), it will not accept it.
scanerss understands (and accepts) only addresses that start with http: but not ones that start with
feed:

so i recorded it as: http://www.ezrss.it/feed/ in that form it is accepted.
if you look at point 2 in your tutorial (http://www.ezrss.it/faq/) there too it is recorded as http.

everything worked properly until sunday. but since monday, scanerss can no longer read the feed.


i believe the reason might be this:

today if i write http://www.ezrss.it/faq/ in my browser, it gets redirected to feed://www.ezrss.it/faq/
my browser can handle feed: addresses and so it properly recovers and displays the feed.

but when scanerss tries to access that and it too gets redirected to feed://... it stops because it does
not understand/handle addresses in the feed:// form.


my point is that, since it was working up to sunday, that redirection was introduced then.
and i believe and hope it should be easy to remove.

in other words: if when i write http://www.ezrss.it/faq/ in my browser it will remain http:// rather than
being changed into feed:// , it will once again be accessible by scanerss too.

thank you.


[#169284] Written by: tfeserver [20/10/2011, 09:35]
i don't think the "feed://" is provided by the web page http://www.ezrss.it .

look's more to be an issue with your app.
[#169288] Written by: Tuttle [20/10/2011, 10:52]
Quote by tfeserver
i don't think the "feed://" is provided by the web page http://www.ezrss.it .

look's more to be an issue with your app.

in order to reply with more data i made a few experiments and the result was unexpected:

i currently am following 8 feeds with scanerss and they all work except ezrss.it. this tells me that
scanerss is basically working.

>> i tested some of the other feeds with my browser and surprisingly discovered they all change to
feed:// so that's not directly the problem.

scanerss truly has some limitations, as you say, but it's working with every other rss feed and was
handling ezrss.it too up to a few days ago.

when ezrss.it stopped working i had not changed anything, so i still believe that the cause is some
change in the ezrss.it response/format/??? that was introduced last weekend, and that impacted some
scanerss limitation/weakness.
i still hope that it can be identified and reversed/undone.


i'm not pointing fingers. i'm only testing and supplying information hoping i or someone else can find
out what happened, be it the feed or the program, or what else, so that i can have that feed working
again in my bt client.

[#169301] Written by: FuzzFuzz [20/10/2011, 17:00]
looks like the dtd declaration is now broken which may explain the problems seen by tuttle.

looking at a random show, here's what i get:

<?xml version="1.0" encoding="utf-8"?>
<!doctype torrent public "-//bittorrent//dtd torrent 0.1//en" "http://xmlns.ezrss.it/0.1/dtd/" ;>
<rss version="2.0">
<channel>

going to http://xmlns.ezrss.it/0.1/dtd/ returns a directory listing, with a dtd file in it. i'm
assuming by the fact that it's called index.dtd that's meant to be auto-served by the webserver but
obviously isn't.

java xml parsers, as used by rss scanners in vuze, tend to want to validate the dtd unless told
otherwise. when trying to get the dtd they instead end up with an html file and the dtd obviously
fails to validate and all kind of errors ensue.

so, fixing this should be a simple matter of either updating the dtd declaration to point to the
real dtd / removing the declaration completely or updating the webserver config to serve index.dtd
by default.
[#169309] Written by: Dungogvolts [20/10/2011, 19:35]

guys i don
[#169311] Written by: qwertylesh [20/10/2011, 19:59]
somethings definitely different since the change of servers.

since the rss had came back up my sickbeard was able to use it perfectly, all up until about 5 - 6 days ago where it states
it can no longer connect.

luckily given that it is a python based automator, i should easily be able to rewrite it to feed:// but if this whole dtd server-
side thing is the root cause then i wont be able to do anything

i've gone back to manual snatching now but i patiently wait and hope that it can be resolved to function more like it did on
the old server so sickbeard works again :>

i love the rss, for the time it was working with sickbeard it spoiled me. ^_^
[#169316] Written by: Dungogvolts [20/10/2011, 21:15]
Quote by dungogvolts

guys i don
[#169359] Written by: sasha81 [21/10/2011, 11:20]
hey guys, any idea why the new the walking dead is showing on the site but not on the rss?
[#169361] Written by: tfeserver [21/10/2011, 12:00]
[#169365] Written by: Tuttle [21/10/2011, 13:24]
Quote by fuzzfuzz
looks like the dtd declaration is now broken which may explain the problems seen by
tuttle.
.........
so, fixing this should be a simple matter of either updating the dtd declaration to point to the
real dtd / removing the declaration completely or updating the webserver config to serve index.dtd
by default.


thank you very much.

you know the inner workings of scanerrs enough to catch the problem.

now i believe it's only a matter of implementing one of the fixes you suggest, that luckily seem quite
simple.


please novaking, can this be done? i, and other users too, would really appreciate.

thank you.
[#169376] Written by: NovaKing (Administrator) [21/10/2011, 17:35]
Quote by fuzzfuzz
looks like the dtd declaration is now broken which may explain the problems seen by
tuttle.

looking at a random show, here's what i get:

<?xml version="1.0" encoding="utf-8"?>
<!doctype torrent public "-//bittorrent//dtd torrent 0.1//en" "http://xmlns.ezrss.it/0.1/dtd/" ;>
<rss version="2.0">
<channel>

going to http://xmlns.ezrss.it/0.1/dtd/ returns a directory listing, with a dtd file in it. i'm
assuming by the fact that it's called index.dtd that's meant to be auto-served by the webserver but
obviously isn't.

java xml parsers, as used by rss scanners in vuze, tend to want to validate the dtd unless told
otherwise. when trying to get the dtd they instead end up with an html file and the dtd obviously
fails to validate and all kind of errors ensue.

so, fixing this should be a simple matter of either updating the dtd declaration to point to the
real dtd / removing the declaration completely or updating the webserver config to serve index.dtd
by default.


this has been fixed.