Hi,

we use the actual stable version of pound 2.6 in production environment.
We have a customer login page from where we redirect our customers to the 
special product page they will use.

In this redirect (its done on the backend servers) url we build in the user 
credencials and encrypt these data with rc4crypt. After encrypting the url 
parameters, we use the php function urlencode to make the encrypted data 
for browsers acceptable.
So the final redirect link will look like this example:


https://www.example.com/?login=%81%00x%D5%3D2%C5%DC%E4%9B%CBy%8D%CE%8C%9C%DC%8CV%C0%91%A7%C2F%8C%5B%1DL%1E%9D%1D%B4%A0f%7DS%A3%87y8%82%1Co%02q

As you can see, there is a %00 in the data part.
Before pound version 2.6 we used pound version 2.4 and it worked fine.

But with version 2.6 the client (browser) got the message "This method may 
not be used.".
We could not find the 501 in the Backend logs.

Its a pound 501 response: config.c:    res->err501 = "This method may 
not be used.";

How could we avoid this error message?
Is there a config flag for this checks?

Thank you for reading
Matthias    

Reply via email to