Feature #68
Return data source error 500's from source-[name] scripts to debug interface
| Status: | Closed | Start: | 05/15/2009 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assigned to: | jacobsj | % Done: | 100% |
|
| Category: | - | |||
| Target version: | Caller ID Superfecta v 2.1.0 |
Description
The PhoneSpamFilter produces a 500 error - leading to a not found result.
As these sources will all get bogged down from time to time - we should consider a limited number of auto retries when the data source detects a 500 error.
Update: It is not a good idea to include the retries. Instead, we will now pass the error 500's back to the debug ui so the user knows that the site is being reached, but is then failing with an internal error 500.
History
Updated by jacobsj over 2 years ago
- Status changed from New to Feedback
I think this is probably a bad idea. We have many sources available, and if a source failed, it will likely fail again in the few micro seconds between the first and second try. I think we'll only be wasting the callers time if we are retrying failed sources.
Updated by tshif over 2 years ago
Ok - then perhaps we can talk about returning a 500 error code back through debug so the end user will be able to tell that the site was in fact reached - but delivered an "internal error" message. That is in keeping with the purpose of the debug area - would it be hard to deploy?
Updated by jacobsj over 2 years ago
- % Done changed from 0 to 90
This should be completed and working now. Someone please verify and close.
Updated by tshif over 2 years ago
- Subject changed from Data source error 500's need limited auto retrys in all source-[name] scripts to Return data source error 500's from source-[name] scripts to debug interface
- Status changed from Feedback to Resolved
Updated by tshif over 2 years ago
- % Done changed from 90 to 80
Incorrect results posted. Entry removed.
Updated by tshif over 2 years ago
Q: Is this deployed in all source scripts? (return 500 error to debug)
Updated by jacobsj over 2 years ago
This is deployed so that any script using curl will show failure errors. This should show us any error, not only 500. so 404 errors and others should be displayed as well.
Updated by tshif over 2 years ago
- Status changed from Resolved to Closed
- Assigned to set to jacobsj
- % Done changed from 80 to 100
Error 500 was successfully passed back to debug. No readily available way to test beyond this.