Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Catching 302 #12

Open
funkju opened this issue Jan 2, 2014 · 1 comment
Open

Catching 302 #12

funkju opened this issue Jan 2, 2014 · 1 comment

Comments

@funkju
Copy link

funkju commented Jan 2, 2014

Hi,

I don't know the status of this project, whether or not it is being actively developed, but the following setup is not working:

var porter = Porter({
.....
}).on({
302: function(err, response){
console.log(err, response);
}
});

If I replace 302 with other return codes (i.e. 200, 500) then it catches the status, but it will not catch 302.

Any ideas why?

@heapwolf
Copy link
Owner

heapwolf commented Jan 3, 2014

Hmm not sure, I'd be happy to look into it though :)

On Thursday, January 2, 2014, funkju wrote:

Hi,

I don't know the status of this project, whether or not it is being
actively developed, but the following setup is not working:

var porter = Porter({
.....
}).on({
302: function(err, response){
console.log(err, response);

}

});

If I replace 302 with other return codes (i.e. 200, 500) then it catches
the status, but it will not catch 302.

Any ideas why?


Reply to this email directly or view it on GitHubhttps://github.com//issues/12
.

Paolo Fragomeni
Founder, @Oqulr
github.com/hij1nx
twitter.com/hij1nx

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants