ankitgoswami97 / rainmeter

Automatically exported from code.google.com/p/rainmeter
0 stars 0 forks source link

Unable to parse HTTPS page #141

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. trying to parse https://stat.byfly.by:443/KK_ABS_WEB_DB.CallHPage?
p_logname=login&p_pwd=pwd

the page can be opened in browser without any problem.

2. So can one parse an secured page? May be the problem that server 
couldn't identify the type of browser?
3.

What is the expected output? What do you see instead?

after using WebParser I see only result in skin: "403 Forbidden
You don't have permission to access /KK_ABS_WEB_DB.CallHPage
on this server."

What version of the product are you using? On what operating system?
v. 1.1, Win7 64

Original issue reported on code.google.com by seliva...@gmail.com on 29 Jan 2010 at 10:43

GoogleCodeExporter commented 8 years ago
I think the cause of this problem to be a method of user authentication and is 
not a
URI scheme (https). Webparser supports only the user authentication by "GET" 
method
like "Basic Authentication". e.g. https://user:password@example.com/
Even if the site is https if such an attestation method used, the server will 
return
the correct response. (Gmail feed is the exactly example.) However, if the 
server
uses the authentication by the method such as "POST", Webparser will be able to
receive only the login page or 401.

In such a case, I think that we have only the way to parse by using Webparser 
after
the source is downloaded to the local by using the other program like cURL.

Original comment by kenz0.sa...@gmail.com on 30 Jan 2010 at 5:44

GoogleCodeExporter commented 8 years ago

Original comment by kenz0.sa...@gmail.com on 13 Mar 2010 at 6:50