Quoting from the HTTP specification for 400.x error codes:

&gt; The 4xx class of status code is intended for cases in which the client
&gt; seems to have erred. Except when responding to a HEAD request, the
&gt; server SHOULD include an entity containing an explanation of the error
&gt; situation, and whether it is a temporary or permanent condition. These
&gt; status codes are applicable to any request method. User agents SHOULD
&gt; display any included entity to the user.

It is best practice to include the error message as an entity in the body of the HTTP response - be it JSON, plain text, formatted HTML, or whatever other format you may want to utilize.

It is better to have error details in the body. Furthermore, many (most / almost all, eg. WSGI) servers and clients do not support changing the name of the error code - treat them as fixed pairs (so eg. 400 is always &quot;Bad Request&quot; and not &quot;Bad Request - You Forgot To Specify The User ID&quot;). Even if they won&#39;t break, they won&#39;t care about your special name for specific error code.

The error does not belong in the body. It belongs in the Warning header.

&gt; The Warning general HTTP header contains information about possible
&gt; problems with the status of the message.

[Reference][1]

  [1]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Warning

I have implemented the following code:

    module.exports = {
        getDataFromUserGps: function(callback)
        {
            connection.connect();
            connection.query(&quot;SELECT * FROM usergps&quot;, 
    			function(err, results, fields) {
    				if (err) return callback(err, null);
                    return callback(null, results);
    			}
    		); 
            connection.end();
        },
        loginUser: function(login, pass, callback)
        {
            connection.connect();
            connection.query(
                &quot;SELECT id FROM users WHERE login = ? AND pass = ?&quot;,
                [login, pass],
    			function(err, results, fields) 
                {
    				if (err) return callback(err, null);
                    return callback(null, results);
    			}
    		); 
            connection.end();
        },
        getUserDetails: function(userid, callback)
        {
            connection.connect();
            connection.query(
                &quot;SELECT * FROM userProfilDetails LEFT JOIN tags ON userProfilDetails.userId = tags.userId WHERE userProfilDetails.userid = ?&quot;,
                [userid],
                function(err, results, fields)
                {
                    if (err) return callback(err, null);
                    return callback(null, results);
                }
            );
            connection.end();
        },
        addTags: function(userId, tags)
        {
            connection.connect();
            connection.query(
                &quot;INSERT INTO tag (userId, tag) VALUES (?, ?)&quot;,
                [userId, tags],
                function(err, results, fields)
                {
                    if (err) throw err;
                }
            )
            connection.end();
        }
    }

Everything works great only for the first time. If I want to &quot;use&quot; the query for the second time I get the following error:
```
Cannot enqueue Handshake after invoking quit
```
I have tried not to `.end()` connections but it didn&#39;t help.

How can I fix this issue?

Cannot enqueue Handshake after invoking quit

Does anyone can link me to some tutorial where I can find out how to return days , hours , minutes, seconds in javascript between 2 unix datetimes?

I have:

    var date_now = unixtimestamp;
    var date_future = unixtimestamp;

I would like to return (live) how many days,hours,minutes,seconds left from the date_now to the date_future.

Javascript return number of days,hours,minutes,seconds between two dates

I have a REST service that is exposed to iPhone and Android clients. Currently I follow the HTTP codes 200, 400, 401, 403, 404, 409, 500 etc.

My question is where is the recommended place to put the reason/description/cause of the error? Does it make more sense for the REST API to always have custom Reason in the header like so?

    &lt; HTTP/1.1 400 Bad Request - Missing Required Parameters.
    &lt; Date: Thu, 20 Dec 2012 01:09:06 GMT
    &lt; Server: Apache/2.2.22 (Ubuntu)
    &lt; Connection: close
    &lt; Transfer-Encoding: chunked

Or is it better to have it in the Response Body via JSON? 

    &lt; HTTP/1.1 400 Bad Request
    &lt; Date: Thu, 20 Dec 2012 01:09:06 GMT
    &lt; Server: Apache/2.2.22 (Ubuntu)
    &lt; Connection: close
    &lt; Transfer-Encoding: chunked
    &lt; Content-Type: application/json
    { &quot;error&quot; : &quot;Missing Required Parameters&quot; }



Rest error message in HTTP Header or Response Body?

I have a REST service that is exposed to iPhone and Android clients. Currently I follow the HTTP codes 200, 400, 401, 403, 404, 409, 500 etc.
My question is where is the recommended place to put the reason/description/cause of the error? Does it make more sense for the REST API to always have custom Reason in the header like so?
<pre><code class="hljs language-yaml">&#x3C; HTTP/1.1 400 Bad Request - Missing Required Parameters.
&#x3C; Date: Thu, 20 Dec 2012 01:09:06 GMT
&#x3C; Server: Apache/2.2.22 (Ubuntu)
&#x3C; Connection: close
&#x3C; Transfer-Encoding: chunked
</code></pre>
Or is it better to have it in the Response Body via JSON?
<pre><code class="hljs language-yaml">&#x3C; HTTP/1.1 400 Bad Request
&#x3C; Date: Thu, 20 Dec 2012 01:09:06 GMT
&#x3C; Server: Apache/2.2.22 (Ubuntu)
&#x3C; Connection: close
&#x3C; Transfer-Encoding: chunked
&#x3C; Content-Type: application/json
{ "error" : "Missing Required Parameters" }
</code></pre>

I am trying to get Apache HttpClient to fire an HTTP request, and then display the HTTP response code (200, 404, 500, etc.) as well as the HTTP response body (text string). It is important to note that I am using `v4.2.2` because most HttpClient examples out there are from `v.3.x.x` and the API changed greatly from version 3 to version 4.

Unfortunately I&#39;ve only been able to get HttpClient returning the status code **or** the response body (but not both).

Here&#39;s what I have:

    // Getting the status code.
    HttpClient client = new DefaultHttpClient();
    HttpGet httpGet = new HttpGet(&quot;http://whatever.blah.com&quot;);
    HttpResponse resp = client.execute(httpGet);

    int statusCode = resp.getStatusLine().getStatusCode();


    // Getting the response body.
    HttpClient client = new DefaultHttpClient();
    HttpGet httpGet = new HttpGet(&quot;http://whatever.blah.com&quot;);
    ResponseHandler&lt;String&gt; handler = new BasicResponseHandler();

    String body = client.execute(httpGet, handler);

So I ask: **Using the `v4.2.2` library, how can I obtain both status code and response body from the same `client.execute(...)` call?** Thanks in advance!

How to get HttpClient returning status code and response body?

I&#39;m trying to create multithreaded web server in python, but it only responds to one request at a time and I can&#39;t figure out why. Can you help me, please?

    #!/usr/bin/env python2
    # -*- coding: utf-8 -*-
    
    from SocketServer import ThreadingMixIn
    from  BaseHTTPServer import HTTPServer
    from SimpleHTTPServer import SimpleHTTPRequestHandler
    from time import sleep
    
    class ThreadingServer(ThreadingMixIn, HTTPServer):
    	pass
    
    class RequestHandler(SimpleHTTPRequestHandler):
    	def do_GET(self):
    		self.send_response(200)
    		self.send_header(&#39;Content-type&#39;, &#39;text/plain&#39;)
    		sleep(5)
    		response = &#39;Slept for 5 seconds..&#39;
    		self.send_header(&#39;Content-length&#39;, len(response))
    		self.end_headers()
    		self.wfile.write(response)
    
    ThreadingServer((&#39;&#39;, 8000), RequestHandler).serve_forever()

Multithreaded web server in python

&gt; **Possible Duplicate:**  
&gt; [How to download image using requests](https://stackoverflow.com/questions/13137817/how-to-download-image-using-requests)  

&lt;!-- End of automatically inserted text --&gt;

I know that fetching a url is as simple as `requests.get` and I can get at the raw response body and save it to a file, but for large files, is there a way to stream directly to a file? Like if I&#39;m downloading a movie with it or something?

Save a large file using the Python requests library

How can I make an HTTP request from Rust? I can&#39;t seem to find anything in the core library.

I don&#39;t need to parse the output, just make a request and check the HTTP response code.

Bonus marks if someone can show me how to URL encode the query parameters on my URL!

How do I make an HTTP request from Rust?

Consider a large HTTP request:

    POST /upload HTTP/1.1
    Content-Type: multipart/form-data
    Content-Length: 1048576

    ...

The client now begins uploading a megabyte of data, which may take a while.  However, the server determines that HTTP authorization is needed, so it decides it will respond with `HTTP 401 Unauthorized`.

MUST the server wait until it has received the entire request (IE, headers + CRLF CRLF + `Content-Length` bytes) before it can respond?

In practical terms, will such behavior break any browsers?  Do browsers continue uploading the file anyway, or will they stop transmitting if they receive a &#39;premature&#39; response?  

More importantly, in this scenario, will they be able to successfully authenticate and begin the upload again (with credentials), or is it unreliable to cut off the upload like this?

Is it acceptable for a server to send a HTTP response before the entire request has been received?

I&#39;m trying to pass a object via REST web service. Following are my classes explains the functionality that I need using some example codes. 

**Rest Web Service Class method**

    @POST
	@Path(&quot;/find&quot;)
	@Consumes(MediaType.APPLICATION_FORM_URLENCODED)
	@Produces({MediaType.APPLICATION_JSON})
	public Response getDepartments(){
		Response response = new Response();
				
		try {
			
			response.setCode(MessageCode.SUCCESS);
			response.setMessage(&quot;Department Names&quot;);
			Department dept = new Department(&quot;12&quot;, &quot;Financial&quot;);
			response.setPayload(dept);

		} catch (Exception e) {
			response.setCode(MessageCode.ERROR);
			response.setMessage(e.getMessage());
			e.printStackTrace();
		}		
		return response;
	}


**Response Class**

    import java.io.Serializable;
    import javax.xml.bind.annotation.XmlRootElement;
    
    @XmlRootElement
    
    public class Response implements Serializable{
    	
    	private static final long serialVersionUID = 1L;
    
    	public enum MessageCode {
    		SUCCESS, ERROR, UNKNOWN
    	}
    
    	private MessageCode code;
    	private String message;
    	private Object payload;
    	
    	public MessageCode getCode() {
    		return code;
    	}
    	
    	public void setCode(MessageCode code) {
    		this.code = code;
    	}
    	
    	public String getMessage() {
    		return message;
    	}
    	
    	public void setMessage(String message) {
    		this.message = message;
    	}
    	
    	public Object getPayload() {
    		return payload;
    	}
    	
    	public void setPayload(Object payload) {
    		this.payload = payload;
    	}
    }


**Department Class**


    @XmlRootElement
    public class Department implements java.io.Serializable {
    
    	
    	private String deptNo;
    	private String deptName;
    
    
    	public Department() {
    	}
    
    	public Department(String deptNo, String deptName) {
    		this.deptNo = deptNo;
    		this.deptName = deptName;
    	}
    
    	public String getDeptNo() {
    		return this.deptNo;
    	}
    
    	public void setDeptNo(String deptNo) {
    		this.deptNo = deptNo;
    	}
    
    	public String getDeptName() {
    		return this.deptName;
    	}
    
    	public void setDeptName(String deptName) {
    		this.deptName = deptName;
    	}
    
    }

When I make a call to getDepartments method in the rest web service class it returns following exceptions. But If I change the type **Object** of the **payload** to **Department** in the Response class it returns the json response correctly. But since I need to use this Response class for different types of Classes I can&#39;t restring the payload to one class type. Can anyone please help me in this matter?

**Stack Trace** 


    Dec 27, 2012 9:34:18 PM com.sun.jersey.spi.container.ContainerResponse logException
    SEVERE: Mapped exception to response: 500 (Internal Server Error)
    javax.ws.rs.WebApplicationException: javax.xml.bind.MarshalException
     - with linked exception:
    [javax.xml.bind.JAXBException: class Department nor any of its super class is known to this context.]
    	at com.sun.jersey.core.provider.jaxb.AbstractRootElementProvider.writeTo(AbstractRootElementProvider.java:159)
    	at com.sun.jersey.spi.container.ContainerResponse.write(ContainerResponse.java:306)
    	at com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1437)
    	at com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1349)
    	at com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1339)
    	at com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:416)
    	at com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:537)
    	at com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:699)
    	at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
    	at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)
    	at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:401)
    	at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
    	at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
    	at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766)
    	at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:450)
    	at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
    	at org.mortbay.jetty.Server.handle(Server.java:326)
    	at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)
    	at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:945)
    	at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:756)
    	at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:218)
    	at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
    	at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410)
    	at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)
    Caused by: javax.xml.bind.MarshalException
     - with linked exception:
    [javax.xml.bind.JAXBException: class Department nor any of its super class is known to this context.]
    	at com.sun.xml.bind.v2.runtime.MarshallerImpl.write(MarshallerImpl.java:323)
    	at com.sun.xml.bind.v2.runtime.MarshallerImpl.marshal(MarshallerImpl.java:177)
    	at com.sun.jersey.json.impl.BaseJSONMarshaller.marshallToJSON(BaseJSONMarshaller.java:103)
    	at com.sun.jersey.json.impl.provider.entity.JSONRootElementProvider.writeTo(JSONRootElementProvider.java:136)
    	at com.sun.jersey.core.provider.jaxb.AbstractRootElementProvider.writeTo(AbstractRootElementProvider.java:157)
    	... 23 more
    Caused by: javax.xml.bind.JAXBException: class Department nor any of its super class is known to this context.
    	at com.sun.xml.bind.v2.runtime.XMLSerializer.reportError(XMLSerializer.java:250)
    	at com.sun.xml.bind.v2.runtime.XMLSerializer.reportError(XMLSerializer.java:265)
    	at com.sun.xml.bind.v2.runtime.XMLSerializer.childAsXsiType(XMLSerializer.java:657)
    	at com.sun.xml.bind.v2.runtime.property.SingleElementNodeProperty.serializeBody(SingleElementNodeProperty.java:156)
    	at com.sun.xml.bind.v2.runtime.ClassBeanInfoImpl.serializeBody(ClassBeanInfoImpl.java:344)
    	at com.sun.xml.bind.v2.runtime.XMLSerializer.childAsSoleContent(XMLSerializer.java:597)
    	at com.sun.xml.bind.v2.runtime.ClassBeanInfoImpl.serializeRoot(ClassBeanInfoImpl.java:328)
    	at com.sun.xml.bind.v2.runtime.XMLSerializer.childAsRoot(XMLSerializer.java:498)
    	at com.sun.xml.bind.v2.runtime.MarshallerImpl.write(MarshallerImpl.java:320)
    	... 27 more
    Caused by: javax.xml.bind.JAXBException: class Department nor any of its super class is known to this context.
    	at com.sun.xml.bind.v2.runtime.JAXBContextImpl.getBeanInfo(JAXBContextImpl.java:611)
    	at com.sun.xml.bind.v2.runtime.XMLSerializer.childAsXsiType(XMLSerializer.java:652)
    	... 33 more




javax.xml.bind.JAXBException: Class *** nor any of its super class is known to this context

I need to design a RESTful query API, that returns a set of objects based on a few filters. The usual HTTP method for this is GET. The only problem is, it can have at least a dozen filters, and if we pass all of them as query parameters, the URL can get quite long (long enough to be blocked by some firewall).

Reducing the numbers of parameters is not an option.

One alternative I could think of is to make use of the POST method on the URI and send the filters as part of the POST body. Is this against being RESTfull (Making a POST call to query data).

Anyone have any better design suggestions?

Design RESTful query API with a long list of query parameters

In my Ruby on Rails application I tried to upload an image through the POSTMAN [REST][1] client in [Base64][2] format. When I POST the image I am getting a *406 Not Acceptable Response*. When I checked my database, the image was there and was successfully saved.

What is the reason for this error, is there anything I need to specify in my header?

My request:

 URL ---    `http://localhost:3000/exercises.json`

Header:

    Content-Type  -  application/json

Raw data:

    {
        &quot;exercise&quot;: {
            &quot;subbodypart_ids&quot;: [
                &quot;1&quot;,
                &quot;2&quot;
            ],
            &quot;name&quot;: &quot;Exercise14&quot;
        },
        &quot;image_file_name&quot;: &quot;Pressurebar Above.jpg&quot;,
        &quot;image&quot;:&quot;******base64 Format*******&quot;
    }

  [1]: http://en.wikipedia.org/wiki/Representational_State_Transfer
  [2]: http://en.wikipedia.org/wiki/Base64


What is &quot;406-Not Acceptable Response&quot; in HTTP?

While the [HTTP 1.1 spec](http://www.w3.org/Protocols/rfc2616/rfc2616.html) seems to _allow_ message bodies on [DELETE](http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html#sec9.7) requests, it seems to indicate that servers should ignore it since there are no defined semantics for it.

&gt; **4.3 Message Body**
&gt;
&gt; A server SHOULD read and forward a message-body on any request; if the
&gt; request method does not include defined semantics for an entity-body,
&gt; then the message-body SHOULD be ignored when handling the request.

I&#39;ve already reviewed several related discussions on this topic on SO and beyond, such as:

* https://stackoverflow.com/questions/299628/is-an-entity-body-allowed-for-an-http-delete-request
* https://stackoverflow.com/questions/5905916/payloads-of-http-request-methods
* https://stackoverflow.com/questions/978061/http-get-with-request-body

Most discussions seem to concur that providing a message body on a DELETE may be *allowed*, but is generally not recommended.

Further, I&#39;ve noticed a trend in various HTTP client libraries where more and more enhancements seem to be getting logged for these libraries to support request bodies on DELETE. Most libraries seem to oblige, although occasionally with a little bit of initial resistance.

My use case calls for the addition of some required metadata on a DELETE (e.g. the &quot;reason&quot; for deletion, along with some other metadata required for deletion). I&#39;ve considered the following options, none of which seem completely appropriate and inline with HTTP specs and/or REST best practices:

* **Message Body** - The spec indicates that message bodies on DELETE have no semantic value; not fully supported by HTTP clients; not standard practice
* **Custom HTTP Headers** - Requiring custom headers is generally [against standard practices](http://my.safaribooksonline.com/book/-/9781449317904/4dot-metadata-design/id2829455); using them is inconsistent with the rest of my API, none of which require custom headers; further, no good HTTP response available to indicate bad custom header values (probably a separate question altogether)
* **Standard HTTP Headers** - No standard headers are appropriate
* **Query Parameters** - Adding query params actually changes the Request-URI being deleted; [against standard practices](https://stackoverflow.com/questions/2539394/rest-http-delete-and-parameters)
* **POST Method** - (e.g. `POST /resourceToDelete { deletemetadata }`) POST is not a semantic option for deleting; POST actually represents the *opposite* action desired (i.e. POST creates resource subordinates; but I need to delete the resource)
* **Multiple Methods** - Splitting the DELETE request into two operations (e.g. PUT delete metadata, then DELETE) splits an atomic operation into two, potentially leaving an inconsistent state. The delete reason (and other related metadata) are not part of the resource representation itself.

My first preference would probably be to use the message body, second to custom HTTP headers; however, as indicated, there are some downsides to these approaches. 

Are there any recommendations or best practices inline with REST/HTTP standards for including such required metadata on DELETE requests? Are there any other alternatives that I haven&#39;t considered?

RESTful Alternatives to DELETE Request Body

I am writing some code to interface with redmine and I need to upload some files as part of the process, but I am not sure how to do a POST request from python containing a binary file.

I am trying to mimic the commands [here][1]:

    curl --data-binary &quot;@image.png&quot; -H &quot;Content-Type: application/octet-stream&quot; -X POST -u login:password http://redmine/uploads.xml

In python (below), but it does not seem to work. I am not sure if the problem is somehow related to encoding the file or if something is wrong with the headers.

    import urllib2, os

    FilePath = &quot;C:\somefolder\somefile.7z&quot;
    FileData = open(FilePath, &quot;rb&quot;)
    length = os.path.getsize(FilePath)

    password_manager = urllib2.HTTPPasswordMgrWithDefaultRealm()
    password_manager.add_password(None, &#39;http://redmine/&#39;, &#39;admin&#39;, &#39;admin&#39;)
    auth_handler = urllib2.HTTPBasicAuthHandler(password_manager)
    opener = urllib2.build_opener(auth_handler)
    urllib2.install_opener(opener)
    request = urllib2.Request( r&#39;http://redmine/uploads.xml&#39;, FileData)
    request.add_header(&#39;Content-Length&#39;, &#39;%d&#39; % length)
    request.add_header(&#39;Content-Type&#39;, &#39;application/octet-stream&#39;)
    try:
        response = urllib2.urlopen( request)
        print response.read()
    except urllib2.HTTPError as e:
        error_message = e.read()
        print error_message


I have access to the server and it looks like a encoding error:

    ...
    invalid byte sequence in UTF-8
    Line: 1
    Position: 624
    Last 80 unconsumed characters:
    7z&#188;&#175;&#39;&#197;&#208;&#208;&#183;2^&#212;&#248;&#235;4g&#184;R&lt;s&#252;&#240;&#237;6k&#196;&#164;&#170;&#182;!&#187;=}jcdjSP&#250;&#225;-&#186;#&#187;&#196;AtD&#187;H7&#202;!&#230;&#189;]j):

    (further down)

    Started POST &quot;/uploads.xml&quot; for 192.168.0.117 at 2013-01-16 09:57:49 -0800
    Processing by AttachmentsController#upload as XML
    WARNING: Can&#39;t verify CSRF token authenticity
      Current user: anonymous
    Filter chain halted as :authorize_global rendered or redirected
    Completed 401 Unauthorized in 13ms (ActiveRecord: 3.1ms)


  [1]: http://www.redmine.org/projects/redmine/wiki/Rest_api_with_curl

Python POST binary data

I&#39;m using Spring MVC for a simple JSON API, with `@ResponseBody` based approach like the following. (I already have a service layer producing JSON directly.)

    @RequestMapping(value = &quot;/matches/{matchId}&quot;, produces = &quot;application/json&quot;)
    @ResponseBody
    public String match(@PathVariable String matchId) {
        String json = matchService.getMatchJson(matchId);
        if (json == null) {
            // TODO: how to respond with e.g. 400 &quot;bad request&quot;?
        }
        return json;
    }

Question is, in the given scenario, **what is the simplest, cleanest way to respond with a HTTP 400 error**?

I did come across approaches like:

    return new ResponseEntity(HttpStatus.BAD_REQUEST);

...but I can&#39;t use it here since my method&#39;s return type is String, not ResponseEntity.

 

How to respond with HTTP 400 error in a Spring MVC @ResponseBody method returning String?

Using a python flask server, I want to be able to throw an http error response with the abort command and use a custom response string and a custom message in the body

    @app.errorhandler(400)
    def custom400(error):
        response = jsonify({&#39;message&#39;: error.message})
        response.status_code = 404
        response.status = &#39;error.Bad Request&#39;
        return response

    abort(400,&#39;{&quot;message&quot;:&quot;custom error message to appear in body&quot;}&#39;)

But the error.message variable comes up as an empty string.  I can&#39;t seem to find documentation on how to get access to the second variable of the abort function with a custom error handler

how to get access to error message from abort command when using custom error handler

Is there a way to add a global catch-all error handler in which I can change the response to a generic JSON response?

I can&#39;t use the `got_request_exception` signal, as it is not allowed to modify the response (http://flask.pocoo.org/docs/0.10/signals/).
&gt; In contrast all signal handlers are executed in undefined order and do not modify any data.

I would prefer to not wrap the `app.handle_exception` function as that feels like internal API. I guess I&#39;m after something like:

     @app.errorhandler()
     def handle_global_error(e):
         return &quot;Global error&quot;

Note the `errorhandler` does not take any parameters, meaning it would catch all exceptions/status codes which does not have a specific error handler attached to them. I know I can use `errorhandler(500)` or `errorhandler(Exception)` to catch exceptions, but if I do `abort(409)` for example, it will still return a HTML response.

Global error handler for any exception

I was experimenting with a new feature that comes with .net core sdk 2.2 that is supposedly meant to improve performance by around 400%.

Impressive so I tried it out on my ABP (*ASP.NET Boilerplate*) project

`Template asp.net core mvc  4.0.2.0`

I added the following to my `web.mv.cproj` file 

      &lt;PropertyGroup&gt;
        &lt;TargetFramework&gt;netcoreapp2.2&lt;/TargetFramework&gt;
        &lt;AspNetCoreHostingModel&gt;InProcess&lt;/AspNetCoreHostingModel&gt;
      &lt;/PropertyGroup&gt;
    
      &lt;ItemGroup&gt;
        &lt;PackageReference Include=&quot;Microsoft.AspNetCore.App&quot; /&gt;
        &lt;PackageReference Include=&quot;Microsoft.AspNetCore.Razor.Design&quot; Version=&quot;2.2.0&quot; PrivateAssets=&quot;All&quot; /&gt;
      &lt;/ItemGroup&gt;

Unfortunately I do not think this version of the ABP framework is compatible as the project simply fails to run and throws: (eventually)

&gt;HTTP Error 500.30 - ANCM In-Process Start Failure

I checked the logs after setting `stdoutLogEnabled=&quot;true&quot;` in the web.config and re-trying - but no entries.

Has anybody had any success running the current ABP against a asp.net core in process setup?

I&#39;m thinking this may be something only available in ABP vNext.



Content Type	Original Author	Original Content on Stackoverflow
Question	James Cowhen	View Question on Stackoverflow
Solution 1 - Http	Perception	View Answer on Stackoverflow
Solution 2 - Http	Tadeck	View Answer on Stackoverflow
Solution 3 - Http	B Seven	View Answer on Stackoverflow

Rest error message in HTTP Header or Response Body?

Http Problem Overview

Http Solutions

Solution 1 - Http

Solution 2 - Http

Solution 3 - Http

Javascript return number of days,hours,minutes,seconds between two dates

Cannot enqueue Handshake after invoking quit

Attributions