problem with redirect to port 83

[feijo]

Hi All,

I am having the following problem: whenever I try to create a new page, or really submit anything, in the admin part of the website, I get a "forbidden access error:

Apache/2.0.61 (Unix) PHP/5.2.5 mod_pubcookie/3.3.2d Server at mydomain.com Port 83

What happens is that the website redirected to port 83 ->  http://mydomain.com:83/admin/index.php?etc

When I remove the :83 part, it works, but this redirecting keeps coming back. Has anybody seen this error before? I am not sure if this an error on the server side or with my settings?!?

I am using apache 2.0.61, PHP 5.2.5 and MySQL 5.0.51

Thanks for the help,

feijo

[Izal]

ALL port numbers below 1024 are RESERVED and for good reason, mainly because certain protocols or processes are performed on those ports.

Port 83 is for UDP communications.

As HTTP runs on port 80, I do not see how the server can respond to your request at all. Port 83 is not port 80 is it!

[feijo]

Thanks for replying. No, it is definitely port 83. I agree with you, I don't see how the server can respond to any request on port 83 when http runs on port 80. That is why I am reporting this here.

To give some more explanation of this issues: I've worked with other cms's before and they had the same problem, but worse. It seems like whenever the code is communicating with the database, the data is routed through port 83, maybe that has something to do with php? I noticed that cmsms does not have this issue with the front end of the website. I haven't seen any port 83 issues and I think that might be due to the config settings: $config['root_url'] , thus manually overriding the path. I am not an expert in these things, so please correct me if I am wrong.

One last things: when I go to the login screen for the back-end it says:    3. Popup windows must be allowed for the following address: mydomain.com:83 . If I can somehow apply a trick to the system settings that no communication is routed through port 83, that should fix it.

Anyway, I hope the issue is clearer now. Any advice on this topic is welcome.

Thanks

[Izal]

You can not just pick and chose what port you want to use, you have to make configuration changes and that has issues with routing of traffic should a collision happen.

You will NEVER as previously stated get HTTP on port 83 until you make the configuration changes needed.

If you have access to the servers router (assuming you have access to it) you can set up an external port to route traffic from one port to another. Under these conditions it is possible to set up a http://mydomain.com:8080 and have port 8080 routed to port 80 or some servers will when configured listen for connections on port 8080 but then fail to respond to port 80 because they have been changed to another port.

[feijo]

unfortunately, I do not have access to the servers router. I don't want to get http through port 83, I don't want to use the port at all. All communication runs through port 80, but for some reason, the server switches to port 83 and gives a forbidden access warning, as expected. Therefore, I was thinking of maybe adding a script that prevents this switching to port 83. However, if I understand your post correctly, that is not possible. This issue has to be solved on the server end, correct?

Thanks

[Dr.CSS]

This is a server/host issue and has nothing to do with CMS Made Simple...