HTTP 100 response in GCF connector

Hi:

I have built a simple connector the purpose of which is to provide a single sign on point for a student email system. Having followed the basic outline of a connector, and verified the sequential actions that need to transpire to effect a login....the connector responds with an HTTP 100 (Continue) after the login form is posted, and then immediately followed by an HTTP 500. The back end HTTP server is IIS 6.0 - does this have anything to do with it? Has anyone encountered such an occurrence before?

Cheers
Tony

0
No votes yet

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

HTTP 100 then 500

Appears to be the User-Agent value in the HTTP request headers. I downloaded the user agent extension for Firefox, and set the agent to the one emitted from Luminis via uPortal (I imagine), that being, "Jakarta Commons-HttpClient/2.0rc2", and can now simulate the 500 error at will.

User-Agent modification

I seem to be answering all my own questions :-) I've posted this just in case anyone wishes to change the "user-agent" header line sent by the Jakarta commons http client. This was the problem in my case - the receiving system could not parse the standard Jakarta commons user agent setting (as such, it should be their [receiving systems] responsibility to correct a bug in their implementation, but in the interests of expediency, I have researched a fix).

The Commons http client will use the value of a system property called "httpclient.useragent" (if defined) as the value of "User-Agent", rather than the standard "Jakarta Commons-HttpClient/2.0rc2"

One must edit the virtual web servers config/jvm12.conf file to effect this change, and add a line similar to that below:

jvm.option=-Dhttpclient.useragent="Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.8) Gecko/20061025 Firefox/1.5.0.8"

This will make the servlet requester "impersonate" a Firefox 1.5.0.8 browser. This modification has been tested under Luminis 3.3.1 and 3.3.3.

cheers

just to let you know I found this useful
thanks