Hi. I have a problem with the Javascript when a html containing frameset is invoked through Pluggable protocol. with JavaScript i am communicating with another frame by calling a JS function lies in another frame. unfortunately i always get permission denied error even though my accessing host and protocol are same. is anyone faced similar problem with pluggable protocol? The same html page and javascript communication with frames works with HTTP protocol Thank you Raghav
wrote in message news:1118845396.875421.252690@f14g2000cwb.googlegroups.com > I have a problem with the Javascript when a html containing frameset > is invoked through Pluggable protocol. with JavaScript i am > communicating with another frame by calling a JS function lies in > another frame. unfortunately i always get permission denied error > even though my accessing host and protocol are same. is anyone faced > similar problem with pluggable protocol? > > The same html page and javascript communication with frames works with > HTTP protocol Do you implement IInternetProtocolInfo on your APP? If so, how? Be particularly careful with ParseUrl using PARSE_SECURITY_URL and PARSE_SECURITY_DOMAIN options. -- With best wishes, Igor Tandetnik With sufficient thrust, pigs fly just fine. However, this is not necessarily a good idea. It is hard to be sure where they are going to land, and it could be dangerous sitting under them as they fly overhead. -- RFC 1925
No i haven't implemented IInternetProtocolInfo interface? can you provide me with some example please where you use this PARSE_SECURITY_URL and PARSE_SECURITY_DOMAIN options? Regards Raghav
i honored the IInternetProtocolInfo interface now and implemented the parseUrl method by considering only the parse_security_url flag. seems parse_security_domain is optional and now there are no permission denied errors between frames to communicate to each other. thanks igor ciao raghav
Dear Raghavalu! I had the same problem. You must do something in SsPlugProt::ParseUrl, if the ParseAction == PARSE_SECURITY_URL. My simple solution is: switch (idParseAction) { case PARSE_SECURITY_URL: // fill resultbuffer and return S_OK swprintf(pwzResult, L"%s", L"prot:"); *pcchResult=wcslen(pwzResult)+2; return S_OK; default: return E_NOTIMPL; } // switch Plese look here: http://groups.google.de/group/microsoft.public.inetsdk.programming.urlmonikers/browse_frm/thread/95082403bbecec2e/bb440a062ec25210?hl=de&lr=&ie=UTF-8&oe=UTF-8&rnum=4&prev=/groups%3Fq%3Dframes%2Bpluggable%2Bprotocols%26hl%3Dde%26lr%3D%26ie%3DUTF-8%26oe%3DUTF-8%26selm%3DOHWCM9o4%2524GA.245%2540cppssbbsa05%26rnum%3D4#bb440a062ec25210 Best Regards, Stefan Raghavulu schrieb: > i honored the IInternetProtocolInfo interface now and implemented the > parseUrl method by considering only the parse_security_url flag. seems > parse_security_domain is optional and now there are no permission > denied errors between frames to communicate to each other. > > thanks igor > > ciao > raghav
