You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wink.apache.org by "Bryant Luk (JIRA)" <ji...@apache.org> on 2009/08/24 01:12:00 UTC
[jira] Created: (WINK-144) Client should use
application/octet-stream when no Content-Type specified
Client should use application/octet-stream when no Content-Type specified
-------------------------------------------------------------------------
Key: WINK-144
URL: https://issues.apache.org/jira/browse/WINK-144
Project: Wink
Issue Type: Bug
Components: Client
Affects Versions: 0.1
Reporter: Bryant Luk
Fix For: 0.2
The client should use application/octet-stream when no Content-Type header is specified with the server side response. This should be consistent with server side behavior when no Content-Type is specified.
I have an integration test that shows this but still trying to figure out an easier way to expand the client tests.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (WINK-144) Client should use
application/octet-stream when no Content-Type specified
Posted by "Bryant Luk (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WINK-144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bryant Luk resolved WINK-144.
-----------------------------
Resolution: Fixed
Assignee: Bryant Luk
> Client should use application/octet-stream when no Content-Type specified
> -------------------------------------------------------------------------
>
> Key: WINK-144
> URL: https://issues.apache.org/jira/browse/WINK-144
> Project: Wink
> Issue Type: Bug
> Components: Client
> Affects Versions: 0.1
> Reporter: Bryant Luk
> Assignee: Bryant Luk
> Fix For: 0.2
>
> Attachments: WINK-144.patch
>
>
> The client should use application/octet-stream when no Content-Type header is specified with the server side response. This should be consistent with server side behavior when no Content-Type is specified.
> I have an integration test that shows this but still trying to figure out an easier way to expand the client tests.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (WINK-144) Client should use
application/octet-stream when no Content-Type specified
Posted by "Bryant Luk (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WINK-144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bryant Luk closed WINK-144.
---------------------------
> Client should use application/octet-stream when no Content-Type specified
> -------------------------------------------------------------------------
>
> Key: WINK-144
> URL: https://issues.apache.org/jira/browse/WINK-144
> Project: Wink
> Issue Type: Bug
> Components: Client
> Affects Versions: 0.1
> Reporter: Bryant Luk
> Assignee: Bryant Luk
> Fix For: 0.2
>
> Attachments: WINK-144.patch
>
>
> The client should use application/octet-stream when no Content-Type header is specified with the server side response. This should be consistent with server side behavior when no Content-Type is specified.
> I have an integration test that shows this but still trying to figure out an easier way to expand the client tests.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (WINK-144) Client should use
application/octet-stream when no Content-Type specified
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WINK-144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12750004#action_12750004 ]
Hudson commented on WINK-144:
-----------------------------
Integrated in Wink-Trunk-JDK1.5 #127 (See [http://hudson.zones.apache.org/hudson/job/Wink-Trunk-JDK1.5/127/])
Should use octet-stream for content type when null
See []
> Client should use application/octet-stream when no Content-Type specified
> -------------------------------------------------------------------------
>
> Key: WINK-144
> URL: https://issues.apache.org/jira/browse/WINK-144
> Project: Wink
> Issue Type: Bug
> Components: Client
> Affects Versions: 0.1
> Reporter: Bryant Luk
> Fix For: 0.2
>
> Attachments: WINK-144.patch
>
>
> The client should use application/octet-stream when no Content-Type header is specified with the server side response. This should be consistent with server side behavior when no Content-Type is specified.
> I have an integration test that shows this but still trying to figure out an easier way to expand the client tests.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (WINK-144) Client should use
application/octet-stream when no Content-Type specified
Posted by "Bryant Luk (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WINK-144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bryant Luk updated WINK-144:
----------------------------
Attachment: WINK-144.patch
Simple fix.
> Client should use application/octet-stream when no Content-Type specified
> -------------------------------------------------------------------------
>
> Key: WINK-144
> URL: https://issues.apache.org/jira/browse/WINK-144
> Project: Wink
> Issue Type: Bug
> Components: Client
> Affects Versions: 0.1
> Reporter: Bryant Luk
> Fix For: 0.2
>
> Attachments: WINK-144.patch
>
>
> The client should use application/octet-stream when no Content-Type header is specified with the server side response. This should be consistent with server side behavior when no Content-Type is specified.
> I have an integration test that shows this but still trying to figure out an easier way to expand the client tests.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.