Skip to content
This repository was archived by the owner on Jan 30, 2020. It is now read-only.

Conversation

@asgrim
Copy link
Contributor

@asgrim asgrim commented Jun 6, 2015

As per the discussion in zendframework/zendframework#7368 this change adds a new
method \Zend\Http\Response->isGone() to determine if the status code is
a "410 Gone". This works exactly the same as the similar methods like
isNotFound simply by checking the status code.

This change takes the opinion that a 410 Gone should not be included in
the isNotFound() method. Further discussion can be seen in the issue.

This was originally opened on zendframework/zendframework#7536.

@mwillbanks
Copy link
Contributor

@asgrim could you please change the target of this to the develop branch?

As per the discussion in zendframework/zendframework#7368 this change adds a new
method \Zend\Http\Response->isGone() to determine if the status code is
a "410 Gone". This works exactly the same as the similar methods like
isNotFound simply by checking the status code.

This change takes the opinion that a 410 Gone should not be included in
the isNotFound() method. Further discussion can be seen in the issue.
@asgrim asgrim force-pushed the add-isgone-to-response branch from 71e1d75 to be17318 Compare July 19, 2015 22:36
@asgrim asgrim closed this Jul 19, 2015
@asgrim asgrim deleted the add-isgone-to-response branch July 19, 2015 22:36
@asgrim asgrim restored the add-isgone-to-response branch July 19, 2015 22:36
@asgrim asgrim deleted the add-isgone-to-response branch July 19, 2015 22:38
@asgrim asgrim restored the add-isgone-to-response branch July 19, 2015 22:38
@asgrim
Copy link
Contributor Author

asgrim commented Jul 19, 2015

Gone to #11

@asgrim asgrim deleted the add-isgone-to-response branch August 4, 2016 15:46
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants