Nginx URL rewriting issue -

-

i need nginx rewriting. have script running follows

http://domain.com:2095/secretkey/something

now above command takes user ip address automatically , want rewrite follows

https://subdomain.domain.com/secretkey/something

i using following rule not working.

 server { listen ip:443; server_name subdomain.domain.com location / {              rewrite ^(.*)$ $1?ip=$remote_addr break;              proxy_pass http://127.0.0.1:2095; } }


Comments

Post a Comment

Popular posts from this blog

sequelize.js - Sequelize group by with association includes id -

-
so when requesting group sequelize follows: return models.workingcalendar .findall({ attributes: [ 'workingcalendar.periodid', 'workingcalendar.date', 'period.name' ], include: [ { model: models.period, attributes: [] } ], where: { getsudoid: currentgetsudo.id, unitplantid: unitplantid }, group: ['workingcalendar.periodid', 'workingcalendar.date', 'period.name'], }); sequelize run query: select [workingcalendar].[id], [workingcalendar].[periodid], [workingcalendar].[date], [period].[name] [workingcalendars] [workingcalendar] left outer join [periods] [period] on [wor...
Read more

mongodb - Multiple $and with multiple $or in $match mongoose -

-
expected condition if(pid==req.session.pid && ((status==0 && statusdate1>=somedate)||(status==1 && statusdate2>=somedate)|| (status==2 && statusdate3>=somedate)||(status==0 && statusdate1>=somedate))) i have tried writing below $match statement meet above condition, reason not expected. var match = { $match: { $and: [ { practiceid: req.session.p_id }, { $or:[{status : 0, statusdate1:{$gte:somedate}}] }, { $or:[{status : 1, statusdate2:{$gte:somedate}}] }, { $or:[{status : 2, statusdate3:{$gte:somedate}}] }, { $or:[{status : 3, statusdate4:{$gte:somedate}}] }] } } could please point me in right direction? update tried below versions, still did not expecting. attempt 1 var match = { $match: { $and: [ { practiceid: req.session...
Read more

Teradata TPT_INFRA: TPT02640: Error: Conflicting column count -

-
i facing issues in teradata parallel transporter while loading data test dev environment. table structure same, face error tpt_infra: tpt02640: error: conflicting column count. source column count (20) target column count (13). export_operator: tpt12108: output schema not match data select statement check schema file have generated. seems issue source file , schema file generated.
Read more