Problem with lighttpd

  • Seems the lighttpd has a bit different behaviour (changes the request_uri variable):

    2017-05-06 15:42:29: (response.c.339) -- splitting Request-URI
2017-05-06 15:42:29: (response.c.340) Request-URI     :  /wp-content/uploads/2017/04/00430012.jpg?debug=true
2017-05-06 15:42:29: (response.c.341) URI-scheme      :  http
2017-05-06 15:42:29: (response.c.342) URI-authority   :  fisher.photography
2017-05-06 15:42:29: (response.c.343) URI-path (raw)  :  /wp-content/uploads/2017/04/00430012.jpg
2017-05-06 15:42:29: (response.c.344) URI-path (clean):  /wp-content/uploads/2017/04/00430012.jpg
2017-05-06 15:42:29: (response.c.345) URI-query       :  debug=true
2017-05-06 15:42:29: (response.c.339) -- splitting Request-URI
2017-05-06 15:42:29: (response.c.340) Request-URI     :  /wp-content/plugins/adaptive-images/adaptive-images-script.php
2017-05-06 15:42:29: (response.c.341) URI-scheme      :  http
2017-05-06 15:42:29: (response.c.342) URI-authority   :  fisher.photography
2017-05-06 15:42:29: (response.c.343) URI-path (raw)  :  /wp-content/plugins/adaptive-images/adaptive-images-script.php
2017-05-06 15:42:29: (response.c.344) URI-path (clean):  /wp-content/plugins/adaptive-images/adaptive-images-script.php
2017-05-06 15:42:29: (response.c.345) URI-query       :

    It would be much more reliable if a parameter also could used instead the server varialbe (like ?url=$1 where the $1 the original uri).

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Takis Bouyouris

    (@nevma)

    Hello there, my friend,

    Thank you for bringing up this issue. We were not aware of it! We will give it some thought in future versions, although I am not sure how we could uniformly tackle the fact that different servers might produce different Request URIs. It is something to sleep on.

    About your suggestion to add a ?url=$1 I’m afraid it would only be meaningful for debugging purposes. We want the plugin to run as intuitively, transparently and automatically as possible and this would require the theme developer to adapt their images’ url structure to a very specific case.

    In addition, putting a file path on a url parameter poses some security concerns that need to be addressed very carefully if one wants to be 100% sure. I am not so sure we want to get into those yet priority-wise.

    Cheers,
    Takis

    Thread Starter fisherhu

    (@fisherhu)

    Thank you for your reply.
    For the parameter I believe no change required on the theme side, the lighttpd passes the full (or partial) uri to the php script, just like the server variable.

    The security concern is a different and real problem indeed. I will try the srcset trick to see if it is implemented correctly nowadays.

    Plugin Author Takis Bouyouris

    (@nevma)

    Hmm, let me see if I can understand this correctly, because I am not a Lighttpd expert. Are you saying that there could be a something like a server rewrite that automatically translates the urls of images into internal url parameters that the plugin could use?

    If that is so, then, yes, it is probably something not too difficult to incorporate. Do you think you could elaborate on this a little bit more? Perhaps illustrate it with an example?

    Cheers,
    Takis

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Problem with lighttpd’ is closed to new replies.