[
https://issues.apache.org/jira/browse/SHINDIG-1112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12731018#action_12731018
]
Chris Chabot commented on SHINDIG-1112:
---------------------------------------
Not that it matters to terribly much (and thanks for accepting our policies):
The "Derivative Works" that the APL referrers to describes existing projects
that are included in another project. For example PHP Shindig uses JSMin,
PHPUnit and the Zend Framework, and for such project (which can only be used if
they have compatible licenses) we need to make a reference in our NOTICE file:
http://svn.apache.org/repos/asf/incubator/shindig/trunk/php/NOTICE. That's what
Section 4(3) of the APL is referring too.
A patch on the other hand is a modification/addition to an existing project, as
such shindig does not 'derive' from an external work, but instead it is part of
the Shindig project it's self.
I'm glad to see you're taking a healthy interest in the licensing situation,
and I hope I described the situation sufficiently
> SignedFetcher doesn't forward gadgets.io.RequestParameters.HEADERS
> ------------------------------------------------------------------
>
> Key: SHINDIG-1112
> URL: https://issues.apache.org/jira/browse/SHINDIG-1112
> Project: Shindig
> Issue Type: Bug
> Components: PHP
> Affects Versions: 1.0
> Reporter: Johan Euphrosine
> Assignee: Chris Chabot
> Fix For: 1.0
>
> Attachments: proxy-base-convert-post-headers-with-no-copyright.patch
>
>
> When a request a signed, shindig doesn't forwarder
> gadgets.io.RequestParameters.HEADERS,
> Because:
> _POST['headers'] are www-form-encoded, key1=value1&key2=value2
> And:
> BasicRemoteContentFetcher.php expects key1: value1\nkey2: value2
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
