FOSDEM 2017 Open Source Conference - Brussels

2017-01-12 Thread Sharan F

Hello Everyone

This email is to tell you about ASF participation at FOSDEM. The event 
will be held in Brussels on 4^th & 5^th February 2017 and we are hoping 
that many people from our ASF projects will be there.


https://fosdem.org/2017/

Attending FOSDEM is completely free and the ASF will again be running a 
booth there. Our main focus will on talking to people about the ASF, our 
projects and communities.


*_Why Attend FOSDEM?_*
Some reasons for attending FOSDEM are:

1. Promoting your project: FOSDEM has up to 4-5000 attendees so is a
   great place to spread the word about your project
2. Learning, participating and meeting up: FOSDEM is a developers
   conference so includes presentations covering a range of
   technologies and includes lots of topic specific devrooms

_*FOSDEM Wiki *_
A page on the Community Development wiki has been created with the main 
details about our involvement at conference, so please take a look


https://cwiki.apache.org/confluence/display/COMDEV/FOSDEM+2017

If you would like to spend some time on the ASF booth promoting your 
project then please sign up on the FOSDEM wiki page. Initially we would 
like to split this into slots of 3-4 hours but this will depend on the 
number of projects that are represented.


We are also looking for volunteers to help out on the booth over the 2 
days of the conference, so if you are going to be there and are willing 
to help then please add your name to the volunteer list.


_*Project Stickers*_
If you are going to be at FOSDEM and do not have any project stickers to 
give away then we may (budget permitting) be able to help you get some 
printed. Please contact me with your requirements.


_*Social Event*_
Some people have asked about organising an ASF social event / meetup 
during the conference. This is possible but we will need know how many 
people are interested and which date works best. The FOSDEM wiki page 
also contains an 'Arrival / Departure' section so so please add your 
details if you would like to participate.


I hope this helps people see some of the advantages of attending FOSDEM 
and we are looking forward to seeing lots of people there from our ASF 
communities.


Thanks
Sharan

Apache Community Development
http://community.apache.org/


Re: Change the content-length header for other filters

2017-01-12 Thread Andre Rothe
Hi,

I have looked into the ap_get_client_block(), it uses the brigade api too. 
If I would remove the old api calls from mod_WebObjects, how many bytes 
I should read on every call to ap_get_brigade (BLOCK_READ)? Is it necessary
to define a timer, which stops a block read, if I try to read too many bytes? 
Or should I use NONBLOCK_READ?

My last try was, to get only one byte from the client first and then read the 
content-length header again (in the case, that it has been changed by my 
filter) 
and call ap_get_client_block() with the corrected length again. 

But I learned, that my filter collects all bytes of the request body (the 
brigade 
contains EOS then) to process it and a second call to ap_get_client_block() 
returns 
always 0, because req->remaining = 0.

I don't see a chance to implement my filter at the moment. Is it possible to 
use 
mod_proxy? A second server in front of the WebObjects server could re-send the
browser requests with mod_proxy which calls my filter too. Maybe with

SetEnv proxy-sendcl 1

the Content-Length header could be fixed after the filter, just before resend 
the
request to the backend server (WebObjects). But I have to change all response 
links 
(HTML, CSS, Javascript) with mod_proxy_html from the WebObjects server to the 
proxy.
But this is so much overhead to intercept and change a simple request.

Any further ideas?

Thanks a lot
André


 Von:   Eric Covener  
 An:
 Gesendet:   22.12.2016 14:43 
 Betreff:   Re: Change the content-length header for other filters 

On Thu, Dec 22, 2016 at 8:37 AM, Andre Rothe 
 wrote: 
> I don't know, how mod_webobjects will read the request content, 
> but it seems, that my changes on the request are not transparent. 
> It is not a problem of the transmitted data, it is a length problem 
> (if I don't change the content length, the request will be processed). 
 
 
It uses the old ap_get_client_block() interface instead of using the 
bucket brigade directly.  It does appear to copy the content length 
before the first read is performed [meaning your input filter has not 
run for the first time when it looks at the length). 
 
 
--  
Eric Covener 
cove...@gmail.com