Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I had the same requirement to POST gzipped data to a .NET web api controller. I came up with this solution:</p> <pre><code>public class GZipToJsonHandler : DelegatingHandler { protected override Task&lt;HttpResponseMessage&gt; SendAsync(HttpRequestMessage request, CancellationToken cancellationToken) { // Handle only if content type is 'application/gzip' if (request.Content.Headers.ContentType == null || request.Content.Headers.ContentType.MediaType != "application/gzip") { return base.SendAsync(request, cancellationToken); } // Read in the input stream, then decompress in to the outputstream. // Doing this asynronously, but not really required at this point // since we end up waiting on it right after this. Stream outputStream = new MemoryStream(); Task task = request.Content.ReadAsStreamAsync().ContinueWith(t =&gt; { Stream inputStream = t.Result; var gzipStream = new GZipStream(inputStream, CompressionMode.Decompress); gzipStream.CopyTo(outputStream); gzipStream.Dispose(); outputStream.Seek(0, SeekOrigin.Begin); }); // Wait for inputstream and decompression to complete. Would be nice // to not block here and work async when ready instead, but I couldn't // figure out how to do it in context of a DelegatingHandler. task.Wait(); // This next section is the key... // Save the original content HttpContent origContent = request.Content; // Replace request content with the newly decompressed stream request.Content = new StreamContent(outputStream); // Copy all headers from original content in to new one foreach (var header in origContent.Headers) { request.Content.Headers.Add(header.Key, header.Value); } // Replace the original content-type with content type // of decompressed data. In our case, we can assume application/json. A // more generic and reuseable handler would need some other // way to differentiate the decompressed content type. request.Content.Headers.Remove("Content-Type"); request.Content.Headers.Add("Content-Type", "application/json"); return base.SendAsync(request, cancellationToken); } } </code></pre> <p>Using this approach, the existing controller, which normally works with JSON content and automatic model binding, continued to work without any changes.</p> <p>I'm not sure why the other answer was accepted. It provides a solution for handling the responses (which is common), but not requests (which is uncommon). The Accept-Encoding header is used to specify acceptable response encodings, and is not related to request encodings.</p>
    singulars
    1. This table or related slice is empty.
    1. POHow do enable a .Net web-API to accept g-ziped posts
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USkaliatech
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POHow do enable a .Net web-API to accept g-ziped posts
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload