In your GNTP implementation, did you implement the stuff in the Flash
section: http://www.growlforwindows.com/gfw/help/gntp.aspx#flash ?
I have had a couple of users ask why some of the web-based GNTP
solutions arent working with Growl 1.3 now that it support GNTP and
upon investigation, it looks like they are all referring to the
Flash-based GNTP implementations. Flash requires a policy check before
it will communicate over a socket, so the 'server' (Growl, in this
case) has to respond correctly to that request in order to allow GNTP
communication.
> --
> You received this message because you are subscribed to the Google Groups "Growl Development" group.
> To post to this group, send email to growl-de...@googlegroups.com.
> To unsubscribe from this group, send email to growl-developm...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/growl-development?hl=en.
>
http://www.growlforwindows.com/gfw/examples/js/
Just click the 'Register' button and the website should register with
Growl (show up in the Applications list) and then you will get some
options for sending actual notifications. It might work just fine and
maybe the other folks just didnt have something configured correctly.
Anyway, I know you guys are probably super busy right now, so I will
also take a look once I have a chance to upgrade my Mac.
i was finally able to upgrade to Lion and install Growl 1.3 as well.
the Flash-based connections are definitely not work (as reported by
Jae) - nothing happens at all, not even any log messages. that leads
me to believe that nothing is even getting through to Growl, which
could indicate an issue with the Flash policy file handling (since no
socket traffic will be allowed if the policy file response is not
correctly received).
> i also tried installing the growlgntp firefox extension for kicks
> and that is a no go as well (again, i am not sure if it should work on
> a mac or not). i do get this error in console for it though:
>
> 10/5/11 10:10:49.401 AM Growl: There was a missing
> <hashalgorithm>:<keyHash>.<keySalt> with encryption or remote, set
> error and return appropriately
> 10/5/11 10:10:49.401 AM Growl: Error occurred: Error domain
> GrowlNetwork, code 400 (The operation couldn’t be completed. Missing,
> malformed, or invalid key hash string).
> 10/5/11 10:10:49.401 AM Growl: Failed reading with error: Error
> Domain=GrowlNetwork Code=400 "The operation couldn’t be completed.
> Missing, malformed, or invalid key hash string"
> UserInfo=0x7ffb0b02d340 {NSLocalizedFailureReason=Missing, malformed,
> or invalid key hash string}
The Firefox extension uses native sockets, not Flash, so it should
work. The good news is that the TCP packets are indeed getting through
to Growl (as see in the log snippet above and verified in my own
testing). The bad news is that the Growl GNTP handler doesnt like the
requests. The Firefox extension doesnt use any password, so it sends
its headers like:
GNTP/1.0 REGISTER NONE
Application-Name: Firefox
//etc
The Growl log message says that the hash algorithm/hash/salt stuff is
missing, but it should not be required if Growl is set up to use no
password, right? Since the extension is using native sockets, it
should be connecting just like any other local application and should
be allowed to operate with no password, right?
Growl on the Mac may eventually support websockets, but since that
spec is not even finalized yet, GNTP over Flash is the only common
denominator for web-based notifications at the moment.
I did notice that the GNTP spec on the GfW site incorrectly omits the
final / character (creating an invalid xml element), so I tried that
as well, along with a few variations of ways to input the trailing
null byte, but nothing worked. If there is code in Growl to response
to the Flash policy request, it is not being triggered by any of the
inputs that I tried.
On Tue, Oct 4, 2011 at 11:01 AM, Daniel Lee Siemer
Once the source repositories are updated, I might have a peek myself
to see if I can track down the issue.