Some web browsers (with Fetch API) support arbirary HTTP method except 'CONNECT'(reserved) and 'TRACE'(blocked in purpose), some web servers (with Servlet API) support arbirary HTTP method except 'CONNECT' (not implemented) and 'TRACE' (disabled by default).

The HTTP method select box of Postcode contains 7 options, I cannot use arbitrary HTTP methods which I can use with Fetch API, like WebDAV's methods, or custom methods.

To support input of arbitraty HTTP method, one approach is to make the select box editable, e.g. in HTML you can change something like <select name="method"> with <input type="text" name="method" datalist="httpMethods"><datalist id="httpMethods">.

B.T.W:

The RAW format select box of Postcode contains only 4 options, I cannot send arbitrary data formats (content types) which I can send with Fetch API, like 'application/csp-report'.

I'm a Postman user, nowdays Postman becomes unfriendly to my GPU, it comes with various issues: blackscreen/stuck, so I'm looking for a lightweight solution, maybe it's Postcode.

Postman can import/export requests via JSON file. It would be really awesome if the same JSON format could be used to import/export requests to/from Postcode.

Hi,

I tested the extension with a GET API requiring basic auth.
I set the credentials in the "Authorization" tab, and selected the "Basic Auth" option.
Unfortunately it did not work.

It worked instead if I put directly the Authorization header in the header section.

I have not checked if the same problem happens with the bearer token authentication (but it could be quite likely).

Regards.

咋解决

currently when issuing a request to localhost I get
Could not send request Error: unable to verify the first certificate

despite running dotnet dev-certs https --trust first

When sending a POST request with a form-data body, the Content-Type header just contains "multipart/form-data" and thus is missing a boundary.
This results into no form data to be found by the server.

Expected result:
A request with a Content-Type like: "multipart/form-data; boundary=--------------------------636776427956514692483101" is sent.

First of all, Thanks for creating this wonderful extension.

Can we please have a button indicating a copy to the clipboard for the following use cases? As I am into API testing by implementing this would make my task easier a lot.

Thanks,
Sumit

http://test.abc?name=测试，不论发送GET还是POST都会提示无法发送请求

The UI is pretty small. The fonts being thin are not visible properly on a large window.

Either changing the fonts to a bolder variant, or increasing the size of the app based on editor font size could be two solutions.

The other actionable buttons are fine but the input font is illegible.

Here is a screenshot for reference:

How to use graphql requests? I don't know where to set graphql requests

could u support websocket test?

Hello,
I found this extension while searching for alternatives to Thunder client and I was wondering if it would be possible for this project to support publishing to openvsx so that it can be used with coder workspaces.

I was using the library for some simple testing, and got a very obscure issue with binary files not uploading correctly. It looks like they are sent wrongly encoded on the request side.

A simple test case in Node.js:

const fs = require("fs");
const express = require("express");

const app = express();
app.use("/", (req, res) => {
  const writeStream = fs.createWriteStream(req.query.filename || "output.txt");
  req.pipe(writeStream);
  res.send();
});
app.listen(2342);

This creates a HTTP app on port 2342 that writes the body of any request to the filename given as a query parameter, e.g. http://localhost:2342/?filename=uploaded.zip means saving the file to uploaded.zip in the app dir.

If I upload a .zip file like the attached test.zip as a "binary" file via Postcode (latest version, installed today), and try to open the resulting uploaded.zip, it will be invalid.

The same flow works as intended in Postman.

Attachments:

test.zip

As saying in #49, if there are Chinese characters or any characters need to be urlencoding in the params, postcode can't send requests properly, we have to encode the characters manually to send the proper request. It's not convenient.

The current layout is a bit crowded on the vertical side

If we compare it to a similar extension, it has a horizontal layout, which makes much easier to use

The following are few features that I feel would be great if included in postcode:

• Automatically append http:// to the beginning of the URL if not already exists: I often type localhost:3000 on the first try and then append http:// to the beginning on figuring out that something is wrong. Postman by default does this and gives a better user experience. I suppose this is the issue addressed in #31.
• Height adjustable Response-bar: Opening a terminal below the response bar makes it too small. It would be great if the height is adjustable by dragging it.
• Ability to see previous requests: This might seem a little far-fetched, but listing the previous requests in the currently empty sidebar would be great.

PS: I have been using postcode for a while and I think that it has the potential to be the goto extension for all API testing. I feel just a few things are missing that are needed for a better user experience.

Module: https://github.com/postmanlabs/postman-code-generators

How to use a script to insert a dynamic parameter?
This function is available in postman and is very easy to use.

Hi,

I have noticed this behavior:

1. If I post with header "Connection", the corresponding header is sent (OK)
2. If I post with unchecked "Connection" header, the header is nevertheless sent with value close (wrong). In this case it should not be sent, or at least sent with a correct default value, which changed from HTTP1.0 and HTTP1.1 and HTTP2:
   • As ref please see https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Connection
   • In HTTP 1.0 it was close
   • In HTTP 1.1, the connection is kept-alive as default behavior
   • In HTTP2 the header should not be sent at all

Regards

Including headers etc. Possibly saved with a workspace?

Currently you can't save any requests, would be nice to save collections