search

ari-ban / issue-test

0 stars 0 forks source link

Grizzly returns a 200 OK message despite error #243

Closed arinban closed 14 years ago

arinban commented 16 years ago

During the porting of Jetty Java Bayeux client this error was encountered. Jetty client sends messages of content type text/json by default. Grizzly doesn't like this but still it responds with a 200 OK message with no body! An error message would be much better.

Here are packages captured with Wireshark:

                        1. REQUEST ###############

POST /index.html/cometd/handshake HTTP/1.1 Content-Type: text/json;charset=utf-8 Host: lappinn2:8080 Content-Length: 70

[

{"channel":"/meta/handshake","version":"0.9","minimumVersion":"0.9"}

]

                            1. RESPONSE ###############

HTTP/1.1 200 OK Content-Type: text/plain; charset=iso-8859-1 Content-Length: 0 Date: Thu, 04 Sep 2008 20:16:48 GMT

Environment

Operating System: Windows XP Platform: PC

Affected Versions

[1.8.5]

arinban commented 6 years ago
arinban commented 16 years ago

@glassfishrobot Commented Reported by amplus@java.net

arinban commented 16 years ago

@glassfishrobot Commented jfarcand@java.net said: Started...

arinban commented 16 years ago

@glassfishrobot Commented jfarcand@java.net said: First pass.

Sending cometd/src/main/java/com/sun/grizzly/cometd/EventRouterImpl.java Sending cometd/src/main/java/com/sun/grizzly/cometd/standalone/CometdAdapter.java Transmitting file data .. Committed revision 1503.

arinban commented 16 years ago

@glassfishrobot Commented jfarcand@java.net said: Fixed. Added a unit test under cometd/

arinban commented 16 years ago

@glassfishrobot Commented Was assigned to grizzly-issues

arinban commented 7 years ago

@glassfishrobot Commented This issue was imported from java.net JIRA GRIZZLY-243

arinban commented 14 years ago

@glassfishrobot Commented Marked as fixed on Wednesday, December 16th 2009, 6:13:23 pm