[
https://issues.apache.org/jira/browse/SHINDIG-348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12602679#action_12602679
]
Chris Chabot commented on SHINDIG-348:
--------------------------------------
Hmm i'm curious now.
I first checked partuza's code, and i see that it adds a normal &nocache=1 to
the iframe url, and there's no urlencode()'ing going on, so it should just
arrive in the $_GET normally right?
Then i checked here locally, and when i add ?nocache=1 to the partuza url, it
puts that &nocache=1 in the iframe urls, and double checked that it is honored,
and it is.
So in the case of apache + php, it seems to work fine as is..
Maybe this is a lightttpd only issue, that lighttpd is being to smart and
encoding stuff for you? If so you might have a bigger problem then just the
nocache param, since there's a -lot- of params that can be parsed on the url
(container, mid, country, lang, view, parent, st, v, and user prefs).. do those
propagate to the gadgetcontext for you or are they also urlencoded and hence
not being picked up?
It might be a larger issue then if that is the case, and might warrant a more
global solution?
> 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
> 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.
