[ 
https://issues.apache.org/jira/browse/SHINDIG-348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12602742#action_12602742
 ] 

karsten.beyer edited comment on SHINDIG-348 at 6/5/08 11:48 AM:
----------------------------------------------------------------

Hmm. It seems that we are talking about two different issues. Passing of the 
parameters and even encoding (or better not encoding) works just fine with 
lighttpd.

If i append the ?nocache=1 to the partuza URL of for example the profile page, 
this is propagated to the gadget just fine. However this document:

http://www.imeem.com/developers/documentation/os/osdev

describes a way to disable the cache for an application during development by 
adding the ?nocache=1 to the gadget URL (the URL of the XML file). e.g. 
http://www.labpixies.com/campaigns/todo/todo.xml?nocache=1. This parameter is 
obviously urlencoded inside the url parameter of the iframe request url:

http://shindig.kbsilver/gadgets/ifr?synd=default&container=default&viewer=4&owner=4&aid=35&mid=76&country=US&lang=EN&view=home
&parent=http%3A%2F%2Fpartuza.kbsilver&st=PVLpSkznN%2FHsbqhdLCf5dNYodD9i6WBQ0xeSYSnl181
CF86owdRq2IsLZh9u0goSBUiYXoH7O1nk1CnTo1n2sztyxtmDsc2Uan3AbFr0y45cLb6E2Qeq1cd9BUnNax
1u0WAfyFoa4GuRO6FFfl2LRaOL6vRSmEVRl%2B51TnmsiRjSL21E5t92%2Fg%2FZ3Wg%2FlhwqQ1NcG
oq8TaIUVSaHSE0ihFgf%2ByBn1q10c8RCbFZGR316Cgo3&v=70f7d645865ea75d4350e46a95550728
&url=http%3A%2F%2Fopensocial.kbsilver%2Fhellosocialworld2.xml%3Fnocache%3D1#rpctoken=1112629637

The submitted patch will use this parameter to disable caching in addition to 
the one in the partuza url.

EDIT: inserted line breaks into url....


      was (Author: karsten.beyer):
    Hmm. It seems that we are talking about two different issues. Passing of 
the parameters and even encoding (or better not encoding) works just fine with 
lighttpd.

If i append the ?nocache=1 to the partuza URL of for example the profile page, 
this is propagated to the gadget just fine. However this document:

http://www.imeem.com/developers/documentation/os/osdev

describes a way to disable the cache for an application during development by 
adding the ?nocache=1 to the gadget URL (the URL of the XML file). e.g. 
http://www.labpixies.com/campaigns/todo/todo.xml?nocache=1. This parameter is 
obviously urlencoded inside the url parameter of the iframe request url:

http://shindig.kbsilver/gadgets/ifr?synd=default&container=default&viewer=4&owner=4&aid=35&mid=76&country=US&lang=EN&view=home&parent=http%3A%2F%2Fpartuza.kbsilver&st=PVLpSkznN%2FHsbqhdLCf5dNYodD9i6WBQ0xeSYSnl181CF86owdRq2IsLZh9u0goSBUiYXoH7O1nk1CnTo1n2sztyxtmDsc2Uan3AbFr0y45cLb6E2Qeq1cd9BUnNax1u0WAfyFoa4GuRO6FFfl2LRaOL6vRSmEVRl%2B51TnmsiRjSL21E5t92%2Fg%2FZ3Wg%2FlhwqQ1NcGoq8TaIUVSaHSE0ihFgf%2ByBn1q10c8RCbFZGR316Cgo3&v=70f7d645865ea75d4350e46a95550728&url=http%3A%2F%2Fopensocial.kbsilver%2Fhellosocialworld2.xml%3Fnocache%3D1#rpctoken=1112629637

The submitted patch will use this parameter to disable caching in addition to 
the one in the partuza url.


  
> GadgetContext should respect nocache directive in gadget URL
> ------------------------------------------------------------
>
>                 Key: SHINDIG-348
>                 URL: https://issues.apache.org/jira/browse/SHINDIG-348
>             Project: Shindig
>          Issue Type: Improvement
>          Components: Gadget Rendering Server (PHP)
>         Environment: Max OS X, lighttpd, Partuza
>            Reporter: Karsten Beyer
>            Assignee: Chris Chabot
>            Priority: Trivial
>         Attachments: fix-SHINDIG-348-improvement.patch
>
>   Original Estimate: 0.08h
>  Remaining Estimate: 0.08h
>
> If you use partuza as example social network and add a gadget with nocache=1 
> attached as parameter, it is not respected by the rendering server, because 
> the URL of the gadget is encoded in the iframe URL and therefore the nocache 
> is not available inside the globale $_GET array. 
> I think that Shindig should respect the nocache in a gadget URL. 
> Patch is ready and will be submitted in a while.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to