GitHub user Leemoonsoo opened a pull request:

    https://github.com/apache/incubator-zeppelin/pull/863

    Prevent duplicated response header insertion

    ### What is this PR for?
    Headers are inserted twice in http response message after 
https://github.com/apache/incubator-zeppelin/pull/831.
    
    it prevents zeppelin-web development mode working (cd zeppelin-web; grunt 
serve)
    
    
![image](https://cloud.githubusercontent.com/assets/1540981/14892895/e7ed9e7a-0d21-11e6-9ff3-f352d18ca721.png)
    
    This PR provides (dirty) fix for the problem. If anyone knows better way to 
prevent duplicated header insertion, please let me know.
    
    ### What type of PR is it?
    Bug Fix
    
    ### Todos
    * [x] - Prevent duplicated header insertion
    
    ### What is the Jira issue?
    
    ### How should this be tested?
    Check if dev mode works. ie. 'cd zeppelin-web; grunt serve', browse 
http://localhost:9000
    
    or
    
    run `curl -vv http://localhost:8080/api/security/ticket` and see if 
there're duplicated headers
    
    ### Screenshots (if appropriate)
    
    ### Questions:
    * Does the licenses files need update? no
    * Is there breaking changes for older versions? no
    * Does this needs documentation? no


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/Leemoonsoo/incubator-zeppelin 
fix_duplicated_resp_header

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-zeppelin/pull/863.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #863
    
----
commit 76a92be4b866ef5af474b9e96cb9956b2a070952
Author: Lee moon soo <m...@apache.org>
Date:   2016-04-28T16:13:05Z

    Prevent duplicated response header insertion

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to