Databases
StackOverflow2013
Postsdbo
POIs it an acceptable practice to enable UnsafeHeaderParsing by default?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POIs it an acceptable practice to enable UnsafeHeaderParsing by default?
    primarykey
    data
    text
    <p>This is a somewhat subjective question, but I'd like to hear the pros/cons for doing this. I manage an open source project called <a href="http://qdfeed.codeplex.com/" rel="noreferrer">Quick and Dirty Feed Parser</a> and the objective of the project is to make it as seamless as possible to consume RSS and Atom feeds in .NET.</p> <p>One of the issues I ran into fairly early on in the development of the project was that some of the feeds I was using as test cases (namely the <a href="http://news.ycombinator.com/rss" rel="noreferrer">Hacker News RSS feed</a>) used improperly formatted HTTP headers, and the HttpWebRequest class in .NET 1.1 and up promptly throws an "unsafe header" exception whenever you receive one of these headers in a GET request.</p> <p><a href="http://blogs.msdn.com/b/gzunino/archive/2004/09/05/225881.aspx" rel="noreferrer">This change was added in order to put a stop to split-response attacks that were raising security issues at the time .NET 1.1 was released</a>.</p> <p>My issue is thus - I can enable the "useUnsafeHeader" configuration option programmatically, but it does it across ALL HttpWebRequests in that application's context. I have users who've complained about QD Feed Parser being unable to consume valid feeds, and this header issue is why.</p> <p>Right now I have my library set up in such a way that developers who use it have to enable unsafe header parsing themselves, although most of them aren't aware that this is the problem and it creates a support overhead for me. </p> <p>I can simply have Quick and Dirty Feed Parser enable unsafe header parsing by default and force security-concious users to disable it, but I don't want to open up users who don't know any better to security attacks either. What's the best option here?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USAaronontheweb
    1. USAaronontheweb
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POIs it an acceptable practice to enable UnsafeHeaderParsing by default?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POIs it an acceptable practice to enable UnsafeHeaderParsing by default?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POIs it an acceptable practice to enable UnsafeHeaderParsing by default?
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI just visited the project site and noticed there is no "FAQ" page in the first page, though you have documented this issue in "Advanced Usage" somewhere else (not that obviously). Make your documentation predictable and easy to locate can also save you from support overhead.
      singulars
      1. POIs it an acceptable practice to enable UnsafeHeaderParsing by default?
      1. USLex Li
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload