Announcement

Collapse
No announcement yet.

Problem accessing passowrd protected directory after move to https

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • [Forum] Problem accessing passowrd protected directory after move to https

    I have an online "form" for people to register certain classic cars with a national registry. It's a simple html form that, when submitted, simply emails the info to the national registrar. I have the form in a special directory, such as: https://www.myforum.com/formdir/modelform.html. In one of my forums, I have a "sub-forum" set up as a "link" forum such that, when someone clicks the link they are re-directed to the aforementioned form page.

    I have always had the directory password protected (done via cPanel) so that anyone accessing the form that sits in that (formdir) directory would be presented with a drop-down asking them to enter a "guest" user name and a specific password they all have. Up until recently, this has worked perfectly (and kept bots from filing out the form).

    However, now that I have moved the site from Http to Https, this scheme is no longer working. If I type the URL to the form in directly to the browser, it works fine - I get the drop down asking for credentials and then am taken to the form. But, when I click on the "Link Forum" to be re-directed to that file, it does not give me the dropdown to enter name/password for the directory.
    Instead, I get a 401 "Unauthorised" error. Clicking on the link is supposed to do a re-direct to the desired page but it doesn't ask for the directory credentials. I do have the URL in the Link Forum settings set to https and not http.

    Any ideas that might be causing the issue? Thanks in advance for any help.
    Basil

  • #2
    I am not sure how this is related to vBulletin itself. You need to discuss the issue with your hosting provider on why the HTML file is giving you an unauthorized error.
    Translations provided by Google.

    Wayne Luke
    The Rabid Badger - a vBulletin Cloud customization and demonstration site.
    vBulletin 5 Documentation - Updated every Friday. Report issues here.
    vBulletin 5 API - Full / Mobile
    I am not currently available for vB Messenger Chats.

    Comment


    • #3
      I'm not sure either, sir, but I thought I'd ask in case some other user of Vbulletin had run into the same or similar issue. My site is not "hosted" by a third party hosting company - it resides on my own dedicated server. As far as I can tell the issue only happens when I access the "registry form" by clicking the "Link forum" link, which yields a URL like:

      https://www.myforum.com/forum/forumdisplay.php?84-Registry - which is supposed to redirect to: https://www.myforum.com/formdir/modelform.html

      The directory "formdir" is password protected and when I was using the unsecured http:// for my site, the "Link" forum would re-direct perfectly and I'd get the drop-down asking for user name and password in order to access the registration form in that directory. Since, if I go directly to https://www.myforum.com/formdir/modelform.html in my browser, I still get the drop-down asking for credentials, I thought the issue "might" be something in the way "forum display.php" is handling the redirect for an https:// URL. Thus, I thought it just "might" be something in Vbulletin that I need to tweak. I can't find anything in my server settings that would account for the issue, which only occurred when trying to access the form via the "link forum" (e.g., redirect using the forumdisplay.php function.

      Hope that makes sense.

      Comment


      • #4
        UPDATE: (In case anyone else ever runs into this). It turns out to have been a simple solution. All I had to do was clear my browser cache and now it works as it should. Sorry for the bother,

        Comment


        • #5
          This provides a bit more information and explains how vBulletin may be involved.

          In the vBulletin code, when you do a HTTP redirect off a forum, it sends the 302 (found) code. Seems your server lets this through to do the authorization.

          If you're not using HTTP, it sends a 301 (permanently moved) code. For some reason this is causing authorization to fail and that is why you get a 401 (authorization required) error. You need to configure the server to offer authorization on this code as well.
          Translations provided by Google.

          Wayne Luke
          The Rabid Badger - a vBulletin Cloud customization and demonstration site.
          vBulletin 5 Documentation - Updated every Friday. Report issues here.
          vBulletin 5 API - Full / Mobile
          I am not currently available for vB Messenger Chats.

          Comment


          • #6
            Originally posted by Wayne Luke View Post
            This provides a bit more information and explains how vBulletin may be involved.

            In the vBulletin code, when you do a HTTP redirect off a forum, it sends the 302 (found) code. Seems your server lets this through to do the authorization.

            If you're not using HTTP, it sends a 301 (permanently moved) code. For some reason this is causing authorization to fail and that is why you get a 401 (authorization required) error. You need to configure the server to offer authorization on this code as well.
            Thanks, but see my update. Turns out to have been an easy fix. I just had to clear my browser cache and viola, it started working as it should. Go figure.

            Comment

            widgetinstance 262 (Related Topics) skipped due to lack of content & hide_module_if_empty option.
            Working...
            X