FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian Development

 
 
LinkBack Thread Tools
 
Old 05-26-2011, 11:51 AM
Ian Jackson
 
Default Getting good bug reports

Russell Coker writes ("Re: Getting good bug reports"):
> Would someone who wants to write a HTTP client bug reporting tool really be
> prevented because they have to setup their own server too?

That would just result in their mail server being blocked by DSA or
owner@bugs.

Ian.


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 19934.16074.63311.574584@chiark.greenend.org.uk">h ttp://lists.debian.org/19934.16074.63311.574584@chiark.greenend.org.uk
 
Old 05-26-2011, 12:21 PM
Patrick Strasser
 
Default Getting good bug reports

schrieb Ian Jackson am 2011-05-25 13:46:
> I wrote:
>> Brian May writes ("Re: Getting good bug reports"):
>>> [ explanation of how reportbug is broken right now ]
>>
>> We could solve this if we can avoid the slippery slope problem.
>>
>> Or to put it another way, I would have no objection to an http
>> submission interface to the BTS, provided that everyone understands
>> and agrees that:

I do note think that it exactly needs to be HTTP, but just something
without MTA and a online connection. HTTP is a well understood protocol,
usually working on port 80 - which is one of the least blocked ports -
with proxies - for those networks where direct access is not allowed.

Using port 80 brings advantages in the aspect of having a direct
connection from most hosts.
Using HTTP brings proxy support, but opens the door for easy to
implement additional bug reporting facilities without the control and
quality constraints that come with reportbug.

Why not use some simple non-HTTP-protocol on port 80?

For the workflow I could imagine:
- Try online submission
- if that fails, try email submission
- if that fails, save the bug report to a file and give the user
instructions how to submit the bug later, maybe from a different host.

Patrick
--
Engineers motto: cheap, good, fast: choose any two
Patrick Strasser <patrick dot strasser at student dot tugraz dot at>
Student of Telemati_cs_, Techn. University Graz, Austria


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: irlgju$rp3$1@dough.gmane.org">http://lists.debian.org/irlgju$rp3$1@dough.gmane.org
 
Old 05-26-2011, 12:43 PM
Fernando Lemos
 
Default Getting good bug reports

On Thu, May 26, 2011 at 9:21 AM, Patrick Strasser
<patrick.strasser@tugraz.at> wrote:
[...]
> Why not use some simple non-HTTP-protocol on port 80?

That tends to break transparent proxying. If port 80 is the only one
you have open, chances are you're behind a transparent proxy as well.

Regards,


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: BANLkTikhWKmYAwCYZRtng86f=O1AjE8cSQ@mail.gmail.com ">http://lists.debian.org/BANLkTikhWKmYAwCYZRtng86f=O1AjE8cSQ@mail.gmail.com
 
Old 05-27-2011, 11:19 AM
Goswin von Brederlow
 
Default Getting good bug reports

Ian Jackson <ijackson@chiark.greenend.org.uk> writes:

> Goswin von Brederlow writes ("Re: Getting good bug reports"):
>> Ian Jackson <ijackson@chiark.greenend.org.uk> writes:
>> > The reason why there is a problem with an http submission interface is
>> > that suddenly every idiot will think "oh I must write a cool ui for
>> > this".
>>
>> But with the tunneling suggested below the cool UI would have to talk
>> smtp as well as http to setup the connection. So actualy doing this via
>> http would be even harder than with plain smtp. So your argument doesn't
>> hold.
>
> Oh I see. I'm not sure that implementing a complicated layered thing
> like that. How would you do sessions, anyway, or would you present
> the whole SMTP session in a single transaction?
>
> I don't think we should be implementing a perverse protocol out of
> fear of a sociopolitical problem unless we don't have another way of
> addressing the sociopolitical problem.

Luckily http already defines that for use in the CONNECT method. This is
usualy used by HTTPS over a HTTP proxy. But it should just as well work
for SMTP over HTTP.

MfG
Goswin


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 87lixsl7bb.fsf@frosties.localnet">http://lists.debian.org/87lixsl7bb.fsf@frosties.localnet
 
Old 05-27-2011, 11:21 AM
Goswin von Brederlow
 
Default Getting good bug reports

Fernando Lemos <fernandotcl@gmail.com> writes:

> On Thu, May 26, 2011 at 9:21 AM, Patrick Strasser
> <patrick.strasser@tugraz.at> wrote:
> [...]
>> Why not use some simple non-HTTP-protocol on port 80?
>
> That tends to break transparent proxying. If port 80 is the only one
> you have open, chances are you're behind a transparent proxy as well.
>
> Regards,

And not transparent ones too. Using http CONNECT is better.

MfG
Goswin


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 87hb8gl78g.fsf@frosties.localnet">http://lists.debian.org/87hb8gl78g.fsf@frosties.localnet
 

Thread Tools




All times are GMT. The time now is 12:28 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org