[Building Sakai] Google & Yahoo not displaying in web content tool

[Charles Severance]

As of r199460 (10 minutes ago) the SAK-12563 branch delegates

sakai.iframe
sakai.iframe.service
sakai.iframe.myworkspace

To the JSR-168 portlet. The other tool ids are still handled by the web-tool.

This means that work on handling the header retrieval and dynamically deciding to do the popup is pretty easy to do at this point.   

If someone want to get started in 

https://source.sakaiproject.org/svn/web/branches/SAK-12563/

I am happy to have other people working on and committing to the SAK-12563 branch as long as we stay in touch.

I will get to it in time - but my planned next steps were to make:

sakai.iframe.site
sakai.iframe.annotatedurl

Delegate to the portlet.

But if a person (or two) were willing to work with me and help figure out how X-frame is supposed to work - I could redirect my efforts to SAK-21624.

The cool news is that you can just check the SAK-12563 out over the web folder, and re-deploy and -- poof --- Frame within a frame vanishes on the gateway page and My Workspace and the Options button turns into the portlet Pencil icon!

/Chuck

On Jan 29, 2013, at 4:37 PM, Matthew Jones wrote:

> This was a feature request we filed.
> 
> https://jira.sakaiproject.org/browse/SAK-21624
> 
> Essentially the server needs to do a request on the URL's headers to see if it actually allows being framed or not. If not they only can have the option to open as a new window. The browser won't allow them to be framed. It would kind of be like what Facebook does when you put in a link, it goes out to the link to see what images are there so it can put a little preview there for you, to see how it needs to be handled.
> 
> This request went along with changing the web content to a portlet (https://jira.sakaiproject.org/browse/SAK-12563) 
> 
> 
> On Tue, Jan 29, 2013 at 4:14 PM, Sam Ottenhoff <ottenhoff at longsight.com> wrote:
> Yep, X-Frame-Options:
> 
> $ curl -I http://www.google.com/
> 
> HTTP/1.1 200 OK
> Date: Tue, 29 Jan 2013 21:13:24 GMT
> Expires: -1
> Cache-Control: private, max-age=0
> Content-Type: text/html; charset=ISO-8859-1
> P3P: CP="This is not a P3P policy! See http://www.google.com/support/accounts/bin/answer.py?hl=en&answer=151657 for more info."
> Server: gws
> X-XSS-Protection: 1; mode=block
> X-Frame-Options: SAMEORIGIN
> Transfer-Encoding: chunked
> 
> 
> 
> On Tue, Jan 29, 2013 at 4:12 PM, Beth Kirschner <bkirschn at umich.edu> wrote:
> I vaguely remember this was by design, but does anyone recall the specifics as to why content in pages such as www.google.com and www.yahoo.com wouldn't display within a Sakai web content tool?
> 
> - Beth
> 
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
> 
> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
> 
> 
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
> 
> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
> 
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
> 
> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20130201/d6440fd3/attachment.html