The Wiert Corner – irregular stream of stuff

Jeroen W. Pluimers on .NET, C#, Delphi, databases, and personal interests

  • My badges

  • Twitter Updates

  • My Flickr Stream

  • Pages

  • All categories

  • Enter your email address to subscribe to this blog and receive notifications of new posts by email.

    Join 2,514 other followers

Archive for the ‘REST’ Category

(52) You Give REST a Bad Name – YouTube

Posted by jpluimers on 2017/11/02

(Usually the “state transfer” in Representational state transfer fails)

Video via +Kristian Köhntopp “Die 90er haben angerufen und wollen ihre Amiga Videos und ihre Corba Specs zurück haben.” (the 90s called wanting their Amiga Videos and Corba Specs back)



Posted in Communications Development, Development, Fun, HTTP, Internet protocol suite, REST, TCP | Leave a Comment »

Sending various HTTP request kinds using curl

Posted by jpluimers on 2017/07/25

I’ve been using cURL but always had a feeling not to its potential basically because the cURL man page [WayBack] is both massive and lacks concrete useful practical examples.

For instance, I knew about the --header and --verbose options (I always use verbose names even though shorter -H and -v exist) to pass a specific header and get verbose output, but the man page basic examples like this by Tader:

curl --header --verbose "X-MyHeader: 123"

source: How to send a header using a HTTP request through a curl call? – Stack Overflow [WayBack]

There are some more examples at but they’re hardly organised or documented.

So I was really glad I found the below answer [WayBack] by Amith Koujalgi to web services – HTTP POST and GET using cURL in Linux – Stack Overflow.

But first note that recent versions (around 7.22 or higher) of cURL now need to combine the --silent and --show-error (or in short -sS) parameters to suppress progress but show errors: linux – How do I get cURL to not show the progress bar? – Stack Overflow [WayBack]

Back to the examples

Read the rest of this entry »

Posted in *nix, Communications Development, cURL, Delphi, Development, HTTP, https, Internet protocol suite, JavaScript/ECMAScript, JSON, Power User, REST, Scripting, Security, Software Development, TCP, TLS, XML, XML/XSD | 1 Comment »

Postman offers free (small-project) API developer tools – Open Source Insider

Posted by jpluimers on 2017/07/19

Cool: [WayBackPostman offers free (small-project) API developer tools – Open Source Insider.

I’ve used the [Archive.isPostman – Chrome Web Store for HTTP/HTTPS API testing using various REST services. It’s awesome even though unlike the postmanlabs/postman-chrome-extension-legacy: Postman REST Client Chrome Extension (Legacy Version) it’s not open source any more as it now can run server side and has an API of itself [WayBack].

Get it at [WayBackPostman | Supercharge your API workflow. Available for Mac OS X, Windows, Linux and Chrome users.


Posted in Communications Development, Development, HTTP, Internet protocol suite, REST, SOAP/WebServices, Software Development, TCP | 2 Comments »

Some ChromeCast URLs

Posted by jpluimers on 2017/02/01

I need to check these against a Chromecast v2 as the below URLs are from a v1 device:

More is possible by using cURL: Chromecast Hacking Has Begun |

sleep 8h; while true; do
curl -H "Content-Type: application/json" -X POST -d 'v=somevideo';




Posted in Chromecast, Communications Development, Development, Google, Hardware Interfacing, HTTP, https, Internet protocol suite, REST, Security, TCP | 3 Comments »

Some notes and links on hacking a Philips TVs TCP ports

Posted by jpluimers on 2017/01/25

In my case this is about a Philips 42PFL7676H TV, but this likely applies to many Philips TVs from the 2009-2012 era.

According to nmap, these ports are open:

1925/tcp open unknown syn-ack
2323/tcp open 3d-nfsd? syn-ack
49153/tcp open upnp syn-ack Philips Intel UPnP SDK 1.4 (Philips Smart TV; UPnP 1.0; DLNADOC 1.50)

TCP port 1925 is actually implementing the jointSPACE REST API over HTTP which has some nice documentation (also locally on your TV).

PCremote implements this and is easy to install: just download (or git clone) the html locally or to a web-server and try it, or even easier: browse to the site. You can even use it on your Raspberry Pi. There is also support for jointSPACE it in agocontrol.

Two nice threads about it from the Philips support forum:

TCP port 2323 seems to be the voodooport which should enable you to do DirectFB Voodoo.

Jean-Marc Harvengt (software engineer at Philips) showed a nice demo (see video below) on using VooDoo. I wish he had published the source code.

TCP port 49153 also hosts an HTTP server. The base URL I could find information about is It seems that nmrDescription.xml has to do with DLNA and upnp.

Later on I found that my brothers 32PFL7675H TV should also support JointSPACE, but that it had to be activated:

AFTER upgrading to the new firmware, jointSPACE NEEDS TO BE ACTIVATED by entering the following digits sequence while watching TV (WatchTV activity): “5646877223

Source: jointSPACE TVs Developers

Before activation, only port was open 49153. After that, port 2323 was open as well. But the app doesn’t work on this TV. This does work however: Philips MyRemote – Android Apps on Google Play


Read the rest of this entry »

Posted in Communications Development, Development, Hardware Interfacing, HTTP, Internet protocol suite, REST, TCP | Leave a Comment »

%d bloggers like this: