Jump to content


Photo

Not catching URI with DLL


  • Please log in to reply
3 replies to this topic

#1 delphidude

delphidude

    Advanced Member

  • uniGUI Subscriber
  • PipPipPipPip
  • 190 posts
  • LocationNorway

Posted 15 May 2018 - 02:11 PM

Hi,

 

Running as localhost I can easily catch the PATH_INFO part of a URI, like http://localhost:8077/test

 

But not when using a DLL under Apache, only get HTTP Exception: "HTTP/1.1 302 Found"

and invalid session if I try in the browser.

 

Then trying to fish out the suggested Location info from the header, I got nothing.

 

I am trying the format https://myserver.com...app.dll/testuri- but not working.

 

I had a rewrite for redirecting http to https, but removing that did not affect this.

Using httpClient.HandleRedirects := True; did not affect the issue.

 

 

Anyone had the same issue, or know about a fix?

 

Update: tried on IIS 8.5, same thing. Only invalid session.

 

Seems like it is not possible to trigger the OnHTTPCommand when running as ISAPI?

 

Nobody ever tried that? This must be a URL rewrite issue...


  • 0

#2 delphidude

delphidude

    Advanced Member

  • uniGUI Subscriber
  • PipPipPipPip
  • 190 posts
  • LocationNorway

Posted 16 May 2018 - 07:52 AM

I wrote those few lines I needed in PHP, since I already have the apache server running.

 

So no crisis at all, as there are many ways to Rome.

 

But still curious :)


  • 0

#3 brunotoira

brunotoira

    Member

  • Members
  • PipPip
  • 40 posts

Posted 17 May 2018 - 11:11 AM

I have the same problem... ISAPI dont catch the URI for example.

 

My website work's fine localhost:8077/api for example

But when convert into ISAPI, i cant call "api" 

give-me error


  • 0

#4 delphidude

delphidude

    Advanced Member

  • uniGUI Subscriber
  • PipPipPipPip
  • 190 posts
  • LocationNorway

Posted 18 May 2018 - 12:26 AM

I noticed there were some "/Handleevent" or whatever PATH_INFO coming in

when it ran as localhost, but silent at HTTPCommand when running under ISAPI.

 

It made me wonder - is the framework sending requests to itself through this

interface, and what if that is blocked under ISAPI? Are we missing something?


  • 0




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users