If you don't think that a recruiter has a good technical understanding of the job she's hiring for, it follows that she may not have screened the candidates correctly. This has happened to me before, and it cost me a day off from an existing job, some heat from my existing bosses at the time (I had to take a day off at an inconvenient time for them) and an irritating amount of travel costs.
Others have noted that this is a list of fairly normal concepts, so definitely not junk, and worth knowing if you're going to continue in the area. If you know Python not C#, a better way than tutorialspoint to get that knowledge is to get a book on Python with a decent section on object oriented programming and work through it. Maybe Steve Lott's 'Building Skills in Python', which is free from his site, even if it is based on 2.6.
(http://buildingskills.itmaybeahack.com/python.html). There was also a bunch of web terminology, which I don't know anything about, except to say it will work better to work through a book/ course on web development rather than looking up an arbitrary selection of terminology (google 'web development with python or other preferred language' to get a start perhaps).
But that isn't practical before the interview - it's just for if you decide that you really want a job in this field.
In the mean time, I would call back the recruiter and press for more details of what kind of work the employer is expecting the successful candidate to do. I'd suggest that sounding interested in the specifics will make you seem more knowledgeable, not less, if you ask in a confident way.
The inappropriate interview I had was a full day affair, and I was already a full time worker. If I had realised how far from my skill set it was, I wouldn't have gone. If your interview is less time commitment you may still think it's worthwhile to go, especially if you don't already have another job, but I think it is useful to get the clearest view possible of whether the employer is really going to be interested in your current skill set.
Preparing for, and attending, interviews is time consuming, and there is an opportunity cost involved. In your case, if you haven't had many interviews, you might decide it's worth the cost just to find out more about jobs in this area, but my advice is to have a clear idea of what you are getting out of attending.