I’ve been using a cfc to help with input sanitizing (portcullis from
riaforge). On the new Lucee server I’m seeing a lot (100’s per hour) of
errors"
“invalid call of the function filterTags
(C:\inetpub\wwwroot\CFC\Portcullis.cfc), first Argument (text) is of
invalid type, can’t cast Object type [Struct] to a value of type
[String];invalid call of the function filterTags
(C:\inetpub\wwwroot\CFC\Portcullis.cfc), first Argument (text) is of
invalid type, can’t cast Object type [Struct] to a value of type [String]”
I understand the message, but I don’t understand why I’m getting it. (and
why in Lucee but not CF)
I did redo the CFC because it uses the old style scoping (and rather lose
scoping) but that didn’t seem to help.
This error has no effect on users and doesn’t seem to be an issue at all
for site operation but it’s creating a lot of log files and I’d like to
eliminate it.
I’ve tried wrapping bits in a cftry/catch block but that’s doesn’t seem to
do anything. I’ve also tried dumping the #object# to a wddx packet and
saving to the log file but that hasn’t shown me anything out of the
ordinary.
I’m a bit stumped.
Any thoughts on what might be happening (or a replacement for portcullis)
are much appreciated.
filterTags() expects a string and returns a struct (I downloaded the code
and looked at the function).
The question I have is this: are the url, form and cookie scopes in Lucee
all “flat” in the sense that they only contain strings, and never a nested
struct? I don’t know. The error and your experience seems to indicate that
one of these contains a nested struct and filterTags() doesn’t know how to
deal with that.
Aria Media Sagl
Via Rompada 40
6987 Caslano
Switzerland
+41 (0)91 600 9601
+41 (0)76 303 4477 cell
skype: ariamediaOn Mon, Aug 31, 2015 at 10:11 PM, Jay B <@Jay_B> wrote:
I’m switching from CF8 to Lucee.
I’ve been using a cfc to help with input sanitizing (portcullis from
riaforge). On the new Lucee server I’m seeing a lot (100’s per hour) of
errors"
“invalid call of the function filterTags
(C:\inetpub\wwwroot\CFC\Portcullis.cfc), first Argument (text) is of
invalid type, can’t cast Object type [Struct] to a value of type
[String];invalid call of the function filterTags
(C:\inetpub\wwwroot\CFC\Portcullis.cfc), first Argument (text) is of
invalid type, can’t cast Object type [Struct] to a value of type [String]”
I understand the message, but I don’t understand why I’m getting it. (and
why in Lucee but not CF)
I did redo the CFC because it uses the old style scoping (and rather lose
scoping) but that didn’t seem to help.
This error has no effect on users and doesn’t seem to be an issue at all
for site operation but it’s creating a lot of log files and I’d like to
eliminate it.
I’ve tried wrapping bits in a cftry/catch block but that’s doesn’t seem to
do anything. I’ve also tried dumping the #object# to a wddx packet and
saving to the log file but that hasn’t shown me anything out of the
ordinary.
I’m a bit stumped.
Any thoughts on what might be happening (or a replacement for portcullis)
are much appreciated.
–
See Lucee at CFCamp Oct 22 & 23 2015 @ Munich Airport, Germany - Get your
ticket NOW - http://www.cfcamp.org/
As far as I know, that’s not sufficient to create a singleton, but rather
invites a race condition in the gap between the isDefined test and the
creation of the object.
Better would be:
<cfif not StructKeyExists( application, ‘Portcullis’ )>
filterTags() expects a string and returns a struct (I downloaded the code
and looked at the function).
The question I have is this: are the url, form and cookie scopes in Lucee
all “flat” in the sense that they only contain strings, and never a nested
struct? I don’t know. The error and your experience seems to indicate that
one of these contains a nested struct and filterTags() doesn’t know how to
deal with that.
Aria Media Sagl
Via Rompada 40
6987 Caslano
Switzerland
On Mon, Aug 31, 2015 at 10:11 PM, Jay B <@Jay_B> wrote:
I’m switching from CF8 to Lucee.
I’ve been using a cfc to help with input sanitizing (portcullis from
riaforge). On the new Lucee server I’m seeing a lot (100’s per hour) of
errors"
“invalid call of the function filterTags
(C:\inetpub\wwwroot\CFC\Portcullis.cfc), first Argument (text) is of
invalid type, can’t cast Object type [Struct] to a value of type
[String];invalid call of the function filterTags
(C:\inetpub\wwwroot\CFC\Portcullis.cfc), first Argument (text) is of
invalid type, can’t cast Object type [Struct] to a value of type [String]”
I understand the message, but I don’t understand why I’m getting it. (and
why in Lucee but not CF)
I did redo the CFC because it uses the old style scoping (and rather lose
scoping) but that didn’t seem to help.
This error has no effect on users and doesn’t seem to be an issue at all
for site operation but it’s creating a lot of log files and I’d like to
eliminate it.
I’ve tried wrapping bits in a cftry/catch block but that’s doesn’t seem
to do anything. I’ve also tried dumping the #object# to a wddx packet and
saving to the log file but that hasn’t shown me anything out of the
ordinary.
I’m a bit stumped.
Any thoughts on what might be happening (or a replacement for portcullis)
are much appreciated.
–
See Lucee at CFCamp Oct 22 & 23 2015 @ Munich Airport, Germany - Get your
ticket NOW - http://www.cfcamp.org/
The singleton issue. I’m not really sure about the scope issue. As noted,
this worked without issue on ACF for years. Micha’s post addresses the
difference in usage, but didn’t seem to help.
And I really don’t understand why the exception isn’t causing any client
side issues? I’m not running any kind of error handling for this.>
Well I’m not 100% sure but we’re doing internal testing with a soft launch
of the new site so we’re generating most the traffic. Haven’t heard of any
issues. The CFC has no error handling in it’s original form.
My updated version (with modern scoping scheme) does, but I’ve gone back to
using the stock code until I can figure out what the problem is.On Tue, Sep 1, 2015 at 8:28 AM, Nando Breiter <@Nando_Breiter> wrote:
How do you know the exception isn’t causing an issue for certain requests?
I haven’t examined the code deeply enough to understand how it handles
errors thrown within it, and I’m of course not familiar with your app.
Aria Media Sagl
Via Rompada 40
6987 Caslano
Switzerland
On Tue, Sep 1, 2015 at 4:23 PM, Jay B <@Jay_B> wrote:
The singleton issue. I’m not really sure about the scope issue. As noted,
this worked without issue on ACF for years. Micha’s post addresses the
difference in usage, but didn’t seem to help.
And I really don’t understand why the exception isn’t causing any client
side issues? I’m not running any kind of error handling for this.
–
See Lucee at CFCamp Oct 22 & 23 2015 @ Munich Airport, Germany - Get your
ticket NOW - http://www.cfcamp.org/
So what happens if you ensure that only strings are passed into the
filterTag() function using a conditional to filter out any structs where it
is called? Does that eliminate the error?
Aria Media Sagl
Via Rompada 40
6987 Caslano
Switzerland
+41 (0)91 600 9601
+41 (0)76 303 4477 cell
skype: ariamediaOn Tue, Sep 1, 2015 at 4:32 PM, Jay B <@Jay_B> wrote:
Well I’m not 100% sure but we’re doing internal testing with a soft launch
of the new site so we’re generating most the traffic. Haven’t heard of any
issues. The CFC has no error handling in it’s original form.
My updated version (with modern scoping scheme) does, but I’ve gone back
to using the stock code until I can figure out what the problem is.
On Tue, Sep 1, 2015 at 8:28 AM, Nando Breiter <@Nando_Breiter> wrote:
How do you know the exception isn’t causing an issue for certain
requests? I haven’t examined the code deeply enough to understand how it
handles errors thrown within it, and I’m of course not familiar with your
app.
Aria Media Sagl
Via Rompada 40
6987 Caslano
Switzerland
On Tue, Sep 1, 2015 at 4:23 PM, Jay B <@Jay_B> wrote:
The singleton issue. I’m not really sure about the scope issue. As
noted, this worked without issue on ACF for years. Micha’s post addresses
the difference in usage, but didn’t seem to help.
And I really don’t understand why the exception isn’t causing any client
side issues? I’m not running any kind of error handling for this.
–
See Lucee at CFCamp Oct 22 & 23 2015 @ Munich Airport, Germany - Get
your ticket NOW - http://www.cfcamp.org/
There isn’t any place in the CFC itself that uses any of the scopes
mentioned by nameOn Tuesday, September 1, 2015 at 6:17:06 AM UTC-6, Micha wrote:
In Lucee cookie, url and form always pointing to the scopes with the same
name, in ACF you can overlay the scopes when you have function arguments
with the same name. We did not follow this implementation because it makes
the scope inaccessible.
So if for example “url” is a function argument containing a string, you
have to write “arguments.url”.
Micha
Am Montag, 31. August 2015 schrieb Jay B :
I’m switching from CF8 to Lucee.
I’ve been using a cfc to help with input sanitizing (portcullis from
riaforge). On the new Lucee server I’m seeing a lot (100’s per hour) of
errors"
“invalid call of the function filterTags
(C:\inetpub\wwwroot\CFC\Portcullis.cfc), first Argument (text) is of
invalid type, can’t cast Object type [Struct] to a value of type
[String];invalid call of the function filterTags
(C:\inetpub\wwwroot\CFC\Portcullis.cfc), first Argument (text) is of
invalid type, can’t cast Object type [Struct] to a value of type [String]”
I understand the message, but I don’t understand why I’m getting it. (and
why in Lucee but not CF)
I did redo the CFC because it uses the old style scoping (and rather lose
scoping) but that didn’t seem to help.
This error has no effect on users and doesn’t seem to be an issue at all
for site operation but it’s creating a lot of log files and I’d like to
eliminate it.
I’ve tried wrapping bits in a cftry/catch block but that’s doesn’t seem
to do anything. I’ve also tried dumping the #object# to a wddx packet and
saving to the log file but that hasn’t shown me anything out of the
ordinary.
I’m a bit stumped.
Any thoughts on what might be happening (or a replacement for portcullis)
are much appreciated.
–
See Lucee at CFCamp Oct 22 & 23 2015 @ Munich Airport, Germany - Get your
ticket NOW - http://www.cfcamp.org/
How do you know the exception isn’t causing an issue for certain requests?
I haven’t examined the code deeply enough to understand how it handles
errors thrown within it, and I’m of course not familiar with your app.
Aria Media Sagl
Via Rompada 40
6987 Caslano
Switzerland
+41 (0)91 600 9601
+41 (0)76 303 4477 cell
skype: ariamediaOn Tue, Sep 1, 2015 at 4:23 PM, Jay B <@Jay_B> wrote:
The singleton issue. I’m not really sure about the scope issue. As noted,
this worked without issue on ACF for years. Micha’s post addresses the
difference in usage, but didn’t seem to help.
And I really don’t understand why the exception isn’t causing any client
side issues? I’m not running any kind of error handling for this.
–
See Lucee at CFCamp Oct 22 & 23 2015 @ Munich Airport, Germany - Get your
ticket NOW - http://www.cfcamp.org/
Not 100% sure but we’re doing internal testing with a soft public launch so
we’re generating most of the traffic Haven’t heard of any issues.
The stock code has no error handling but my modified code (with modern
scoping scheme) does. I’ve gone back to the stock though until I can figure
out the problem. FWIW, the error handling didn’t seem to make a difference
for this error in any case.>
Don’t think that’s the issue but I’ll change it as a best practice. (and
thanks for taking the time to research this…above & beyond!)
Are you referring to the singleton issue or my speculation that one of url,
form or cookie scopes may not be flat (contain only strings) in Lucee? If
one of those scopes somehow can contain a nested struct, then that would
explain the error you are getting, and perhaps the solution would be to
filter those out. I’m simply speculating …On Tue, Sep 1, 2015 at 3:07 PM, Jay B <@Jay_B> wrote:
In Lucee cookie, url and form always pointing to the scopes with the same
name, in ACF you can overlay the scopes when you have function arguments
with the same name. We did not follow this implementation because it makes
the scope inaccessible.
So if for example “url” is a function argument containing a string, you
have to write “arguments.url”.
MichaAm Montag, 31. August 2015 schrieb Jay B :
I’m switching from CF8 to Lucee.
I’ve been using a cfc to help with input sanitizing (portcullis from
riaforge). On the new Lucee server I’m seeing a lot (100’s per hour) of
errors"
“invalid call of the function filterTags
(C:\inetpub\wwwroot\CFC\Portcullis.cfc), first Argument (text) is of
invalid type, can’t cast Object type [Struct] to a value of type
[String];invalid call of the function filterTags
(C:\inetpub\wwwroot\CFC\Portcullis.cfc), first Argument (text) is of
invalid type, can’t cast Object type [Struct] to a value of type [String]”
I understand the message, but I don’t understand why I’m getting it. (and
why in Lucee but not CF)
I did redo the CFC because it uses the old style scoping (and rather lose
scoping) but that didn’t seem to help.
This error has no effect on users and doesn’t seem to be an issue at all
for site operation but it’s creating a lot of log files and I’d like to
eliminate it.
I’ve tried wrapping bits in a cftry/catch block but that’s doesn’t seem to
do anything. I’ve also tried dumping the #object# to a wddx packet and
saving to the log file but that hasn’t shown me anything out of the
ordinary.
I’m a bit stumped.
Any thoughts on what might be happening (or a replacement for portcullis)
are much appreciated.
–
See Lucee at CFCamp Oct 22 & 23 2015 @ Munich Airport, Germany - Get your
ticket NOW - http://www.cfcamp.org/
