uShop English (U.S.) for 179!

uStorekeeper English (U.S.) for 149!

 Products
       uTest
       uReserve
       uShop
       uStorekeeper
       uGolf
       uDirectory
       uSignIn
 Tech Support
       Support Policy
       Knowledge Base
            uTest
            uReserve
            uShop
            uStorekeeper
            uGolf
            uDirectory
            uSignIn
       Documentation
       Reference Sites
 Legal
       Software Piracy
       Legal Notices
       Privacy Policy
       Licensing
 Miscellaneous
       Reseller Info
       Contact Us
       Site Map
CGI-intial login

Knowledge Base Lobby : uShop Support Conference : CGI Script Related Problems
Oct-20-17 06:47 AM EST
Original Message
CGI-intial login
Author eci on 02-25-2000 at 14:01 (EST)
I had problems writing to the server, initially.
I believe I have corrected that after deleting the files and reloading them and doing the chmd 755 for the second time.

Now I have run into another problem.

I do not have https certification.
I am having problems with the manger.pl config. and THINK it is due to the SECURE URL https in the config. script. (???)
OR
"SOCKETS" FOR "sendmail" (???)

I get to login and login. I get the following error:

"""Method Not Allowed
The requested method POST is not allowed for the URL /index.html.
Apache/1.3.6 Server at yourwebhost.com Port 443"""

Prior to purchasing this product understood that since we already have authorize.net account, the https is not necessary, however is suggested.

I need to get around the https config.

Help.
E-MAIL AUTHOR | TABLE OF CONTENTS

Table Of Contents
  Solved it. eci, 2000-02-25 21:27:26 (1)

Messages In This Discussion
         1. Solved it.
        Author eci on 02-25-2000 at 21:27 (EST)
For those who come by and want to know how this was solved.....

*METHOD incorrect...

I just happened to be re-checking the manager.pl script and came across the https:// line and noticed that the *ustorekeeper-manager.pl* was *not* there.

Sometime or another during my copy and pasting, I missed getting that in there.

SECURE url....

As far as the https *bypass* (for those who do have authorize.net - and feel they don't want double security) can just simply change the https:// to http://. Much easier than applying for a certificate.
TABLE OF CONTENTS

© 2003 Microburst Technologies, Inc.