jira.codehaus.org

  • Log In Access more options
    • Online Help
    • Keyboard Shortcuts
    • About JIRA
    • JIRA Credits
    • What?s New
  • Dashboards Access more options (Alt+d)
  • Projects Access more options (Alt+p)
  • Issues Access more options (Alt+i)
  • Archiva
  • MRM-757

Need to default mime-type / content-type for unknown types.

  • Log In
  • Views
    • XML
    • Word
    • Printable

Details

  • Type: Bug Bug
  • Status: Open Open
  • Priority: Minor Minor
  • Resolution: Unresolved
  • Affects Version/s: 1.0.1
  • Fix Version/s: Backlog
  • Component/s: repository interface
  • Labels:
    None

Description

As seen in MRM-755, when working with Websphere, the content-type header is required.
Currently, the codebase will only provide mime-type / content-type based on extensions found in the mime-types.txt file.

We should default the mime-type for those types not found.
The suggestion to use octet-stream as the default was raised in the #archiva irc channel.

Issue Links

is related to

Bug - A problem which impairs or prevents the functions of the product. PLXCOMP-103 Content Type is set to null, when mime type is unknown

  • Major - Major loss of function.
  • Open - The issue is open and ready for the assignee to start work on it.

Bug - A problem which impairs or prevents the functions of the product. MRM-755 No content type for .pom files denoted in file "archiva-mime-types.txt" - workaround included

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Improvement - An improvement or enhancement to an existing feature or task. MRM-756 make content-disposition header customisable for some mime-types

  • Minor - Minor loss of function, or other problem where easy workaround is present.
  • Open - The issue is open and ready for the assignee to start work on it.

Activity

  • All
  • Comments
  • Work Log
  • History
  • Activity
Hide
Permalink
Steffen Grunwald added a comment - 15/Apr/08 7:20 AM

I suggested a patch in PLXCOMP-103 for this issue.
That is, don't send the content type header field if the content type is not known.

Show
Steffen Grunwald added a comment - 15/Apr/08 7:20 AM I suggested a patch in PLXCOMP-103 for this issue. That is, don't send the content type header field if the content type is not known.

People

  • Assignee:
    Unassigned
    Reporter:
    Joakim Erdfelt
Vote (0)
Watch (1)

Dates

  • Created:
    30/Mar/08 8:17 PM
    Updated:
    15/Apr/08 7:20 AM
  • Atlassian JIRA (v5.0.4#731-sha1:3aa7374)
  • Report a problem
  • Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.