ct-keycloak-iam VS httpbin

For this exercise, we will use a custom Keycloak server from https://github.com/czetsuyatech/ct-keycloak-iam. This project downloads a specific version of the Keycloak server and builds customizations such as theme, provider, realm, and more.

So something like https://httpbin.org (which BTW recently has some capacity issues)

I've used https://httpbin.org for such a purpose.

What bothers me about Postman is how they took ownership of the popular httpbin project 5 years ago and left it to bitrot. They haven't made a single commit since then, not even dependency upgrades. Now it has acquired 5 years' worth of CVEs in its dependency chain. They receive PRs to fix those issues, but all PRs and issues are ignored.

Why take ownership of the project if when there's no intention of maintaining it from the very beginning? It's almost as if projects like httpbin are detrimental to their business.

https://github.com/postmanlabs/httpbin

use GuzzleHttp\Client as HttpClient; Route::any('/proxy/{path}', function(Request $req, $path) { $client = new HttpClient([ 'base_uri' => 'https://httpbin.org' ]); return $client->request($req->method(), $path); });

let response = try Web.Contents( "https://httpbin.org", [ RelativePath = "/status/codes/418", ManualStatusHandling = {401, 402, 404} & {405..500} ] ) catch (e) => "Error, but we caught it" meta e in response

POST MULTIPART http://httpbin.org/post 'X-Parse-Application-Id':hello X-Parse-REST-API-Key:"world" # DATA first=second # FILES [email protected]/image.jpeg

use strict; use warnings; use feature 'say'; use WWW::Mechanize; my $url = 'https://httpbin.org/headers'; my $mech = WWW::Mechanize->new; $mech->add_header("User-Agent" => "Internet Explorer/6.0"); $mech->add_header("api-key" => "Some API key"); $mech->get( $url ); #say $mech->status; #say '---'; #say $mech->dump_headers; #say '---'; say $mech->content;

httpbin: http://httpbin.org/