Nick's Tech Blog: http

Pages

Showing posts with label http. Show all posts
Showing posts with label http. Show all posts

Thursday, June 14, 2012

TIBCO > HTTP Connection automatically responds to HTTP OPTIONS method

Problem

The default HTTP Connection is automatically responding to HTTP OPTIONS methods, without being processed by my HTTP receiver (I want to be able to process these requests!).

Here is the default response:
HTTP/1.1 200 OK
Server: Apache-Coyote/1.1
Allow: GET, HEAD, POST, PUT, DELETE, TRACE, OPTIONS
Content-Length: 0
Date: Thu, 14 Jun 2012 08:14:35 GMT

Solution

  1. In the "HTTP Connection" Configuration tab, change the Server Type from "Tomcat" to "HttpComponent".
This should allow you to process all HTTP methods.

I'm yet to clarify whether this problem is related to Tomcat (or the HTTP Connection). Please feel free to respond if you find out!

Thursday, May 31, 2012

TIBCO > MimeParts are incorrectly parsed by the HTTP Receiver

Problem

The TIBCO ActiveMatrix BusinessWorks Administration document explains it best (last seen here)
In previous releases, when the content-type of an incoming message was "multipart/*", the first part of the message was presented as the POSTDATA. This is incorrect according to MIME specification.
Solution 
The bw.plugin.http.handleAllMimePartsAsAttachment property fixes this problem.

If this property is set to true and the top-level content-type of the incoming HTTP message is "multipart/*", then an HTTP Receiver will present all the MIME parts as attachments and the POSTDATA field will be empty. If this property is set to false (the default value), backward compatibility is maintained and the first MIME part is presented as the POSTDATA.

N.B. Do not check the Parse Post Method Data field on the HTTP Receiver process starter when this property is set to true. This causes an error to be thrown.
Development
  1. Simply add the following line to your <designer_home>/<version%gt;/properties.cfg file (create it, if it doesn't already exist).
    1. bw.plugin.http.handleAllMimePartsAsAttachment=true
  2. Restart Designer
Runtime (N.B. I haven't tested this yet, feedback warmly welcomed!)
  1. At run time, append it to the deployed .tra file.
See also:
https://www.tibcocommunity.com/thread/13797?tstart=1425