• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

https to apache, but http to WAS

 
Greenhorn
Posts: 23
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I can't find any documentation covering this scenario:

I'm using Apache2 and the WAS plugin.
WAS runs on a separate server than apache.

The WAS server has SSL configured, on port 9443.
This is so you don't need root to start Websphere.

Apache listens on 443.

With the generated plugin-cfg.xml, this scenario won't work:

# Client (HTTPS 443) Apache (HTTPS 9443) WebSphere App server



I get a The host <> on port 443 has not been defined when I hit the web server. If I reconfigure apache to listen on 9443, it works fine.

I could change WAS to listen on 443, but don't like that setup.
Is there a way to change plugin-cfg to understand this "port shift"?

I don't really need https between apache and WAS, it would be better
in terms of perfomance if that traffic is over http.
I can't see a way of getting that to work either.

Regards,
/Tom
[ July 07, 2004: Message edited by: Tom Bombadyll ]
 
Don't get me started about those stupid light bulbs.
reply
    Bookmark Topic Watch Topic
  • New Topic