TeamSoftware Solutions

We are moving form PWB 2 to PWB 3 CEF. Everything is working well, except that as soon as I enable URL.txt, I can't open any urls that are coded to open in a new window. The message is 'The URL "" has been denied'. I do have +about:blank in URL.txt, which I think is supposed to handle this situation. I also have DisableNewWindow=FALSE, DisableNewWindowInit=FALSE.

It doesn't matter what URL I try to open, as long as it has a target="_blank" in the coding, it won't open with the message above. It seems like the filter is kicking in before about:blank loads. Is there anything in PWB.INI or URL.txt that can fix this situation? Thanks for any thoughts. -David

What is the URL of the page with the issue?

With PWB v3 CEF, under certain circumstances web sites will present an empty string for the URL and this will cause the URL filter to default to what is specified in the filter file for "+/-all".

PWB v3.05.0, available on the Beta Downloads page, adds [Security]FilterIgnoreEmpty=Ture to correct for this.

--Scott

Scott, thanks for the reply. I can confirm that using the 3.05.0 beta and setting [Security]FilterIgnoreEmpty=True fixed the problem!
The page I was testing is: https://lincc.ent.sirsi.net/client/en_U ... %7C%7Ctrue

From there, clicking on the Library2Go or 3M Cloud Library link would produce the error before adding the new setting.

Do you know when this feature will go into a production release?

Thanks again,
David

We will be releasing it soon as this seems to be a pretty big issue with the site and there was not much change in PWB to correct it.

--Scott

Hi Scott,

I'm just reporting that Newcastle University are seeing this problem too!

We are using the PWB v 3.0.4.4 (chrome engine) and have just started getting this issue from the off campus links on the page:
http://www.ncl.ac.uk/library/resources/ ... atalogues/
These sites are explicitly included in our URL.txt file, everything else is blocked.

Is the production 3.05.0 version ready to download yet? (Or is the beta sound enough to deploy?)

Thanks,

Paul.

If you turn off the filters with the following is the page denied?

[Security]
CheckURLAccess=False

If the page is allowed after turning off the filter you are blocking something in the page with the filter.

See the following about the PWB filters:
https://www.teamsoftwaresolutions.com/f ... p?f=4&t=13

Using PWB v3 CEF you can turn on the following to only check the mainframe URL.

[Security]
CheckURLMainFrameOnly=True

--Scott

Set the following in your INI file to have PWB indicate what URLs are being denied in the history file.

[Files]
HistoryFile=History.txt

[Security]
WriteHistoryFile=True
LogAccess=True

Here are the history file codes:
https://www.teamsoftwaresolutions.com/f ... ?f=4&t=195

--Scott

Paul,

Thank you, we will delve into it with your configuration.

Have you tried PWB v3.05.0 with the following setting?

[Security]
FilterIgnoreEmpty=True

Does this fix the problem?

--Scott