Spell checking not working (php has openssl and sockets)

[SiGGy]

When I click on "check spelling" it just returns that everything is spelled correctly. However I know it isn't...

Unlike other folks posts I have seen, I do have openSSL and sockets enabled.

PHP CONFIG From a phpinfo();
Compiled with:
'./configure' '--with-mysql' '--with-apxs=/usr/local/apache/bin/apxs' '--with-openssl=/usr/local/ssl' '--enable-sockets'

OpenSSL support    enabled
OpenSSL Version    OpenSSL 0.9.8d 28 Sep 2006
Sockets Support     enabled

Now I can see the SSL connection going to google from the server as seen here when I click on "check spelling" Icon.

[root@mail~]# tcpdump -n -i any tcp and port 443
listening on any, link-type LINUX_SLL (Linux cooked), capture size 96 bytes
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
18:55:57.058890 IP X.X.X.X.41526 > 72.14.203.99.https: S 2072740005:2072740005(0) win 5840
18:55:57.068218 IP 72.14.203.99.https > X.X.X.X.41526: S 1448002372:1448002372(0) ack 2072740006 win 8190
18:55:57.068294 IP X.X.X.X.41526 > 72.14.203.99.https: . ack 1 win 5840
18:55:57.070814 IP X.X.X.X.41526 > 72.14.203.99.https: F 1:1(0) ack 1 win 5840 18:55:57.080507 IP 72.14.203.99.https > X.X.X.X.41526: F 1:1(0) ack 2 win 5720
18:55:57.080577 IP X.X.X.X.41526 > 72.14.203.99.https: . ack 2 win 5840 18:55:57.408932 IP X.X.X.X.41528 > 72.14.203.104.https: S 2071451324:2071451324(0) win 5840
18:55:57.418720 IP 72.14.203.104.https > X.X.X.X.41528: S 2640511288:2640511288(0) ack 2071451325 win 8190
18:55:57.418789 IP X.X.X.X.41528 > 72.14.203.104.https: . ack 1 win 5840 18:55:57.421309 IP X.X.X.X.41528 > 72.14.203.104.https: F 1:1(0) ack 1 win 5840
18:55:57.431620 IP 72.14.203.104.https > X.X.X.X.41528: F 1:1(0) ack 2 win 5720
18:55:57.431680 IP X.X.X.X.41528 > 72.14.203.104.https: . ack 2 win 5840

Any idea why it's not working?
My logs folder doesn't even contain an error file, so I haven't received any errors...

-David

[SiGGy]

Hmm, it's been awhile since I have posted this. I haven't had time to debug it myself. I just disabled Spell checking for now and recommended everyone use Firefox 2.0 for now. Guess I'll have to start playing with it..