Viewing https pages

For general issues related to PWB v2.

Moderators: Tyler, Scott, PWB v2 Moderator

Post Reply
oracwa
Observer
Observer
Posts: 5
Joined: Fri Nov 25, 2005 1:39 am

Viewing https pages

Post by oracwa »

Hi Everyone

Been using V1 for years and it worked great. Had a site upgrade and now 1 gets LOTS of errors. Loaded 2 and had some issues with setting the allowable web pages but finally got that sorted only to come up against an https site that needs to be accessed.

I have included the URL and the IP address of the site but it will not let me access the site.

I have read all I can find but no references to visiting https sites.

Can anyone please help?

THanks

Orac from WA

Scott
Site Admin
Site Admin
Posts: 2530
Joined: Mon Dec 16, 2002 12:31 pm
Location: Rochester, MN
Contact:

Post by Scott »

PWB should have no problems with HTTPS sites.

What, if any error or PWB, messages are you getting?

If it is being blocked by the URL or IP filter, try setting the following in your INI file to get a dialog with the URL that is being blocked.

[Security]
...
DebugAccessString=True
...

--Scott

oracwa
Observer
Observer
Posts: 5
Joined: Fri Nov 25, 2005 1:39 am

Re: Viewing HTTPS pages

Post by oracwa »

Hi again

Did the suggested mod to the INI file and the error

Denied:CheckIPAccess
https://ejournal.csiro.au/cgi-bin/scise ... n=journals

is displayed. I have the following in the IP.txt file
-all
+152.83.8.25

And the following in the URL.txt file
-all
+ejournal.csiro.au

but I still get the error. I have tried another of our https sites and that also fails with the same error.

??

Thanks

Orac from WA

Scott
Site Admin
Site Admin
Posts: 2530
Joined: Mon Dec 16, 2002 12:31 pm
Location: Rochester, MN
Contact:

Post by Scott »

When I ping "ejournal.csiro.au" I get "150.229.2.46" as the IP address. Adding "150.229.2.46" to the IP filter should correct the problem.

Please note, if the site uses JavaScript the "-all" option in the IP filter will deny access to the JavaScript functions since PWB can not resolve the function to an IP address. You should use the URL filter by itself if this is the case.

--Scott

oracwa
Observer
Observer
Posts: 5
Joined: Fri Nov 25, 2005 1:39 am

Post by oracwa »

Hi Guys

After much fiddling, it seems my obsession with security did me in. I was using BOTH the IP.txt and the URL.txt as security to prevent the punters putting in IP addresses into the browser and ending up a hotsex.com.

:^)

Seems that this was causing the error and by removing all of the IP addresses and replacing with +all the problem solved. Of course PBW checks the URL list and if the one typed in (e.g. the IP for hotsex.com) is not in the list, no go!

Thanks for your time.

Cheers

Orac from WA

Scott
Site Admin
Site Admin
Posts: 2530
Joined: Mon Dec 16, 2002 12:31 pm
Location: Rochester, MN
Contact:

Post by Scott »

Instead of adding the "+all" to the IP filter, I would suggest disabling it by setting CheckIPAccess=False in the INI file.

--Scott

I once locked down a computer so much nobody could use it including me, but the computer never had another problem after that.

Post Reply