Hi all, I was testing post-receive hooks [1] the other day and found out that if the URL specified for a post-receive hook contains a query part - it will be discarded before making a POST request to that URL with the JSON body.
I think this behavior limits the usage of post-receive hooks as some cases could need the query part being sent to the URL. For example, I wanted to make a post-receive hook for a blog hosted on GitHub (using GitHub pages) that would essentially enable pubsubhubbub support for the blog. To achieve this, a created a small AppEngine service which needs to receive a pubsubhubbub hub URL and a feed URL via query parameters to notify the pubsubhubbub hub that the feed is refreshed (since this is impossible to do using pre-defined hooks in GitHub). However, if the post-receive hooks system trims the query parameters - the call to the service is useless and there is no other way to call the service in this way. (There are ways to get around this, but those are basically ugly hacks -- e.g. predefining those parameters in the service or passing the parameters not as query parameters but by encoding them in the path part of the URL). Is there a reason for trimming query parameters from the URL and if not - is there a possibility that could be turned of? Thanks! Ivan [1] http://help.github.com/post-receive-hooks/ -- You received this message because you are subscribed to the Google Groups "GitHub" group. To post to this group, send email to git...@googlegroups.com. To unsubscribe from this group, send email to github+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/github?hl=en.
